gritzko

6 ms·

61.
by gritzko 3mo ago
LLM-is-a-compiler is indeed a simplistic approach. I wrote a rebuttal to the yesterday's Cursor post, may reuse it here https://replicated.live/blog/follow-up The idea that a 835-page spec "just exists"
62.
On Cursor's "Agent swarms and the new model economics"(replicated.live)
1 points by gritzko 3mo ago|0 comments
63.
by gritzko 3mo ago
I am afraid the folks are still busy playing with familiar toys. "Let's extract more code out of LLM's inner layers!" SQLite we already have. That's where their "spec" came from. The interesting frontier i
64.
by gritzko 3mo ago
Back in my early career days, CPUs were clocked at 1GHz. That was 20-25 years ago.
65.
by gritzko 3mo ago
Making a high-throughput revision control system is doable, there have been experiments here on HN with git-in-postgres etc. The question is, what is the actual bottleneck here? I made a VCS for LLM assisted work, bootstrapping it on its ow
66.
by gritzko 3mo ago
2*128 is the UUID namespace, which is astronomical. That is like 21 letters. Making one sentence of Shakespeare by random search is strictly 0% chance. SHA256 is ~43 letters then. "LLM broke all of cryptography and creates random data
67.
Tree-of-Life and Evolution of Code(replicated.live)
1 points by gritzko 3mo ago|0 comments
68.
Order and Chaos (256 Shades or Dirtiness)(replicated.live)
1 points by gritzko 3mo ago|0 comments
69.
by gritzko 3mo ago
might be relevant: https://martin.kleppmann.com/2025/12/08/ai-formal-verificati...
70.
by gritzko 3mo ago
Thanks, fixed. The runtime[1] and the scripts[2] are the practical ones. I am separating the old repo[3] into submodules since submodule recursion became smooth in Beagle. [1]: https://github.com/gritzko/jab [2]: http
71.
by gritzko 3mo ago
I am the author. I am trying to limit one post to one page. Most people here are reading reasoning all day, I am afraid. Might get tired. I also aspire to make one post a day. To be continued.
72.
Automating AI Away(replicated.live)
139 points by gritzko 3mo ago|62 comments
73.
by gritzko 3mo ago
I have the last native Fujitsu laptop that is worthy of mention. I am a big fan. Fun story: about 5 years ago they decided to resume their laptop production, and the only practical way was to enroll old retired Japanese workers. I guess, th
74.
Work the Tool to Work the Thing(replicated.live)
1 points by gritzko 3mo ago|0 comments
75.
by gritzko 3mo ago
CommonMark spec[1] is laaarge and not formal (no grammar). StrictMark has block-level[2] and inline[3] grammars, 100+ and 200+ lines of Ragel code respectively. May parse with regexes too, and results will be identical. [1]: https:/&#
76.
by gritzko 3mo ago
About five years ago I faced the fact no two Markdown implementations are fully compatible. I made StrictMark[1], which is a backwards-compatible Markdown dialect with a formal grammar (I use Ragel for parser generation btw). Takes 5-10 min
77.
by gritzko 4mo ago
May look mundane, but there is a funny trend. Git folks rediscover database internals from the first principles.
78.
by gritzko 4mo ago
2010. I remember those times. I was doing these things for science in 2008. Performance-wise, PEX was much faster than DHT. At least, in my setting. This year, I was giving it as an assignment to students. Does not take much time with LLMs.
79.
by gritzko 4mo ago
The question is who maintains it. I think, LLM is the only practical option. In my agent rules, I tell it to maintain INDEX.md on each level. That takes 1 line of instruction and starting with an example file. Then, it self-maintains.
80.
by gritzko 4mo ago
In the Beagle SCM, I am doing my best to simplify that flow, but that is only doable because Beagle has multi-project repos. Still, there are some difficulties with submodule recursion. In the git model, difficult to imagine this working
81.
by gritzko 4mo ago
Every Beagle command: gritzko@spot ~/beagle $ be get 19:07 get ?#0ac49e6a 16:58 post ?0ac49e6a#POST-018 put:/post: banner on stdout 19:07 new beagle/test/be-post-put-banner.sh 19:07 upd dog&
82.
by gritzko 4mo ago
Five is enough. Beagle uses five HTTP verbs: GET, POST, PUT, DELETE, PATCH. And it is syntax-aware. https://replicated.wiki/blog/uris.html
83.
by gritzko 4mo ago
Git vocabulary is workflow-based, i.e. "what we usually do". Unfortunately, the language grew complex and easy to mess up. The problem of NxN interactions: what happens if we do C between A and B? So the idea here is to define ac
84.
by gritzko 4mo ago
The most human-friendly thing is probably natural language. If so, it is LLMs who should have an intuition about the REST interface and its URI syntax. I personally would prefer to glance at it, but not to type it repeatedly. Especially, ha
85.
AI: Surgeon's Assistant or Commodity on a Meter?(replicated.wiki)
3 points by gritzko 4mo ago|0 comments
86.
by gritzko 4mo ago
https://github.com/gritzko/libabc/blob/main/Sx.h https://github.com/gritzko/libabc/blob/main/S.md ABC uses s[2] for slices, g[3] for gauges, b[4] for (ring) buffers.
87.
Beagle: Git, URIs and all the dirty words(replicated.wiki)
30 points by gritzko 4mo ago|8 comments
88.
by gritzko 4mo ago
Nice experiment, but a bit expensive. I work on Beagle, a git-compatible SCM [1]. I use ABC, Abstractionless C [2] dialect with slices, optional range checking, etc. So far, memory safety was the least of my concerns, frankly. Most of the t
89.
by gritzko 4mo ago
I always post this https://www.rte-france.com/en/data-publications/eco2mix/powe...
90.
by gritzko 5mo ago
I live on alpine, in fact.

More ›