gritzko

8 ms·

121.
by gritzko 7mo ago
The actual point of the post: Y.js is slow and buggy.
122.
by gritzko 7mo ago
So is it basically Markdown? The landing does not articulate, unfortunately, what the key contribution is.
123.
by gritzko 8mo ago
Tree-sitter can parse somewhat-bad code. Also, there is an option to pick a codec for a particular file. Might use tree-sitter-C, might use general-text. The only issue here, you can't change the codec and keep nice diffs. So, these ca
124.
by gritzko 8mo ago
I cannot remember a case, in the last 10 years at least, when I committed code that does not compile. Why should I share that? Also, tree-sitter sort of handles that.
125.
by gritzko 8mo ago
(Author) There is a fall-back general-text codec: tokens, no AST (e.g. for Markdown). If that fails (non UTF8), there is the general-blob final-fallback codec (the git mode). The way it makes an AST tree is non-lossy. Additionally, it stam
126.
by gritzko 8mo ago
CRDT's trick is metadata . Good old diff guesses the changes by solving the longest-common-subsequence problem. There is always some degree of confusion as changes accumulate. CRDTs can know the exact changes, or at least guess less
127.
by gritzko 8mo ago
For one merge, yes. The fun starts when you have a sequence of merges. CRDTs put ids on tokens, so things are a bit more deterministic. Imagine a variable rename or a whitespace change; it messes text diffing completely.
128.
by gritzko 8mo ago
Was "sem" named "graft" last week and "got" a week before that? Everyone is vibing so hard it is difficult to keep track of things. Also, idea theft gets to entirely new levels. Bot swarms promote 100% vibed st
129.
by gritzko 8mo ago
I work on AST based revision control. I have a stack of ideas on how to achieve the same Ctrl+W effect with commits/diffs/cherry-picks. All still in flux. If you have some thoughts to share, please do. [1]: https://gith
130.
Iranian strikes on Amazon data centers highlight industry's vulnerability(apnews.com)
7 points by gritzko 8mo ago|0 comments
131.
by gritzko 8mo ago
I only diff the changed files. Producing blob out of BASON AST is trivial (one scan). Things may get slow for larger files, e.g. tree-sitter C++ parser is 25MB C file, 750KLoC. Takes couple seconds to import it. But it never changes, so no
132.
by gritzko 8mo ago
I will ask Claude to open it, thanks!
133.
by gritzko 8mo ago
This will not work for refactors. In fact, any other change will break the hash. I know because I used this approach for quite some time.
134.
by gritzko 8mo ago
At this point, the question is: why keep files as blobs in the first place. If a revision control system stores AST trees instead, all the work is AST-level. One can run SQL-level queries then to see what is changing where. Like - do an
135.
by gritzko 8mo ago
Heh. Find how to grant permissions/ acquire lock in git. You can not. That is fundamental to distributed systems. Downside: harder to think about it all. Upside: a rocket may hit the datacenter. From what I remember about Figma, it can
136.
Beagle SCM: repos, branches, waypoints and milestones(github.com)
3 points by gritzko 8mo ago|0 comments
137.
by gritzko 8mo ago
Don't forget to check the new name with Claude: Are there revision control systems named "got"? Searched the web Searched the web Yes! There is at least one notable revision control system named "Got" — specifically
138.
by gritzko 8mo ago
I tried to control LLM output quality by different means, including fuzzing. Had several cases when LLM "cheated" on that too. So, I have my own shades and grades of being sure the code is not BS.
139.
by gritzko 8mo ago
"Evil maids" (example): I put my laptop into a safe, seal the safe, seal the room, go to breakfast. On return, I see there was cleaning (not the usual time, I know the hotel), the cleaner looks strangely confused, the seal on the
140.
by gritzko 8mo ago
1. Just saying, strange coincidence 2. How can we compare Claude's output in a different language? 3. Detecting break-ins and handling evil-maids: unless the trick is already known on the internets, I do not disclose. Odds are not in m
141.
by gritzko 8mo ago
OK for prototyping. Not OK for prod use if noone actually read it line by line.
142.
by gritzko 8mo ago
I work on a revision control system project, except merge is CRDT. On Feb 22 there was a server break-in (I did not keep unencrypted sources on the client, server login was YubiKey only, but that is not 100% guarantee). I reported break-in
143.
by gritzko 8mo ago
I think I understand the situation.
144.
by gritzko 8mo ago
That is very very interesting. I work on a similar project https://replicated.wiki/blog/partII.html I use CRDT merge though, cause 3-way metadata-less merges only provide very incremental improvements over e.g. git+mer
145.
by gritzko 8mo ago
This is probably the time to add some invitation system like GMail had in the beginning. Or make a shade for accounts <1yr. Or something else, before things get too mixed.
146.
Part II. SCM as a database for the code(replicated.wiki)
2 points by gritzko 8mo ago|0 comments
147.
by gritzko 8mo ago
I was the happy owner of ThinkPad X1 Extreme g1. It had that bug out of the box, new original battery. Once it thermal throttles, it never goes back to full GHz. It throttled pretty soon, cause big CPU small chassis. Yes, I had a script lik
148.
by gritzko 8mo ago
https://replicated.wiki/blog/partII.html
149.
by gritzko 8mo ago
That is JetBrains Mono. HN is using Verdana, I believe, that one is recommended as the most usable common font. Smalltalk is ancient. I would say, Unison is an interesting recent experiment, and there are others. But, I am interested in uni
150.
by gritzko 8mo ago
I am working on AST level revision control and yes, macros make life difficult. On the other hand, merging/diffing on the AST level is fun. https://replicated.wiki/blog/partI.html

More ›