gritzko

4 ms·

31.
by gritzko 2mo ago
The key part: they decided to use the unchanged git codebase as their building block. Likely assuming that the people who wrote the Linux kernel probably knew what they were doing. That explains some features that look bizarre from the gene
32.
by gritzko 2mo ago
In a project with two levels of submodules and tens of worktrees, you cannot "just use git" :/ GitHub does not help much either.
33.
by gritzko 2mo ago
You can get surprisingly far just by using git as a protocol. Such mundane things as tickets and chat logs do not really need any proprietary tech. Think Google OKF. https://cloud.google.com/blog/products/data-anal
34.
by gritzko 2mo ago
git is such a good platform for decentralized tech. Forfeiting that advantage is just criminal. What I really want (and almost have) is a local GitHub for me and agents. With 4+ orchestrators working with a ton of subagents, things get diff
35.
Git Links(replicated.live)
1 points by gritzko 2mo ago|0 comments
36.
by gritzko 2mo ago
I set a line budget for comments (also wiki page parts, chat responses, etc). That only helps when I ask it to do a second pass to reword everything to the budget and add links. I think they tuned it this way to stash reasoning dumps in the
37.
by gritzko 2mo ago
Why use e-mail? That was 20 years ago. I developed my own local setup that is like GitHub for me and agents, see the link. Everything is a repo, may pull and push tickets, docs, everything. That was not a major effort, unless you count 20 y
38.
by gritzko 2mo ago
I strongly disagree with the assumption that GitHub's alternative is another centralized forge. Git itself is perfectly decentralized, as was the original Linux kernel development process. How people managed to put all their eggs in on
39.
Git Links(replicated.live)
1 points by gritzko 2mo ago|0 comments
40.
An office suite for the intelligence age(macro.com)
2 points by gritzko 2mo ago|0 comments
41.
Macro is a unified workspace for teams(github.com)
1 points by gritzko 2mo ago|0 comments
42.
by gritzko 2mo ago
Recently?
43.
by gritzko 2mo ago
If you dont use that regularly, why keep the app?
44.
by gritzko 2mo ago
Yep, tell Claude to spit out a shell script. Use Python if bash is not enough.
45.
by gritzko 2mo ago
That is in fact the difficult part. You have to explain it all coherently while adjusting to the reader's frame. No one does that for no good reason. It is hellish work.
46.
by gritzko 2mo ago
For Macs, there is iA Writer already. Why don't you make something equally polished for other platforms? I am genuinely interested, I always wanted iA Writer for Linux. Everything I tried falls short.
47.
My precious attention (tabular worktree/ticket UI)(replicated.live)
1 points by gritzko 2mo ago|0 comments
48.
by gritzko 2mo ago
Interesting. I use annotations for that. But even if agents ignore them 1 out of 100 cases, I have enough cases here to see it happen.
49.
My Own GitHub: Git, CRDT, Markdown(replicated.live)
1 points by gritzko 2mo ago|0 comments
50.
Git, CRDT, Markdown(replicated.live)
1 points by gritzko 2mo ago|0 comments
51.
My Precious Attention(replicated.live)
1 points by gritzko 2mo ago|0 comments
52.
by gritzko 3mo ago
Java started as a language to write apps on the Internet (applets). Then, it evolved into an elephantine corporate-focused language, because that's where the money is. I remember those Java applets that took minutes to load. The Web wa
53.
Producing ammonia and fertiliser using wind power in Morris, Minnesota(ammoniaenergy.org)
136 points by gritzko 3mo ago|124 comments
54.
by gritzko 3mo ago
I think FireChat was the first one, in 2011.
55.
Libdog: Token-Level Revision Control(github.com)
2 points by gritzko 3mo ago|0 comments
56.
by gritzko 3mo ago
Thanks! It is mathematically rigorous https://replicated.live/blog/status
57.
by gritzko 3mo ago
Great lib. I meant libdog, a different thing. gitoxide is like "git implemented in Rust" while libdog is "git's necessary primitives in C" (objects, packs, sync proto, own index format, diff/merge, etc). As a r
58.
by gritzko 3mo ago
The only way out is malleable software. Have the core data structures and algorithms in a native library. Have a layer of JavaScript/Lua/LISP on top of that. Editable, customizable, reusable. This is not a theory. I work in such a
59.
by gritzko 3mo ago
Spot on. I had my repo messed up more than once. Sometimes it is quick enough to push that to GitHub.
60.
by gritzko 3mo ago
JavaScript did this for the Web back in the day. I work on a malleable git-compatible SCM right now. First I put all the performance-critical parts into a native lib, then happily built my own git(hub) in JavaScript. Tastes differ, someone

More ›