gritzko

9 ms·

181.
by gritzko 10mo ago
Just read AWS or CloudFlare outage postmortems and you will see: are still there, in the happy land.
182.
The Internet's Last Bottleneck(replicated.wiki)
2 points by gritzko 10mo ago|0 comments
183.
by gritzko 10mo ago
Did you read "Parsing JSON is a minefield"?
184.
by gritzko 10mo ago
What can I say. I want all problems in my life to be like that.
185.
by gritzko 10mo ago
Probably, we need a formal data format, because JSON is just a notation. It does not mandate the bit width of numbers, for example, or whether ints are different from floats. Once there is such formal model, we can map it 1:1 between repres
186.
by gritzko 10mo ago
I am a bit saddened by the fact people get obsessed by syntactic innovation or even less than that. Don't we have plenty of urgent problems around us?
187.
by gritzko 10mo ago
Git solves that problem and it definitely exists. Speaking of package managers, it really depends. Like, can we use one SQLite file for that? So easy, why no one is doing that?
188.
by gritzko 10mo ago
Merges require revisioning. JSON or SQL do not have that in the model. This variant of CRDT is actually quite minimalistic.
189.
by gritzko 10mo ago
Let’s make a thought experiment. Suppose that I have a data format and a store that resolves the issues in the post. It is like git meets JSON meets key-value. https://github.com/gritzko/go-rdx What is the probability
190.
by gritzko 10mo ago
It’s all npm on the inside, if I understand correctly.
191.
by gritzko 10mo ago
Sorry, but who are you? Your accounts have no history.
192.
Prediction: AI will make formal verification go mainstream(martin.kleppmann.com)
3 points by gritzko 11mo ago|0 comments
193.
by gritzko 11mo ago
Correct me if I am wrong, but C is the “greatest common denominator” for several decades already. Java, .NET, go, Rust are very much ecosystems-in-themselves. From the practical standpoint, they can not use each other’s code, but they all
194.
by gritzko 11mo ago
The entire Cloud/SaaS story had a lot of happy-path cost optimization. The particular glitch that triggered the domino effect may be irrelevant relative to the fact that the effect reproduces.
195.
by gritzko 11mo ago
Paris Cloudflare Error
196.
by gritzko 11mo ago
Another aspect is the fact this repo reflects Torvalds’ view of the world. He operates in large-ish changesets.
197.
by gritzko 11mo ago
> After extracting a list of every merge conflict in the kernel's Git history, I tried using Mergiraf to resolve them. 6,987 still resulted in conflicts, but 428 were resolved successfully. A much larger fraction of merge conflicts
198.
The first evidence of a take-off in solar in Africa(ember-energy.org)
1 points by gritzko 1y ago|0 comments
199.
by gritzko 1y ago
Is it a binary tree? SQL storage may be an overshoot. Using the RFC 7574 layout, plain files would do fine.
200.
by gritzko 1y ago
idiocracy_window_view.jpg
201.
by gritzko 1y ago
More like a chat server or a sync server. Normal Web server connections are short lived. Flash crowds from HN would give 100K visits a day maybe, that is like 1 or 2 at a time unless you WebSocket them. Imagine what sort of traffic you need
202.
Flattening the stack, reducing the complexity of a JavaScript runtime(github.com)
1 points by gritzko 1y ago|0 comments
203.
by gritzko 1y ago
I was checking Google Maps recently. In such places as Islamabad or Cyprus, residential solar is big. I also hear, the price of panels is low % of the entire installation. What excites me is that solar works one level up. Coal is energy, so
204.
by gritzko 1y ago
France is 60% nuclear
205.
by gritzko 1y ago
lubuv, libevent introduce a layer of abstraction, their own approach to buffer mgmt, etc. If poll() works, better stay with poll(). It is universally portable, things stay pretty clean and simple as a result. Right now I am working on JavaS
206.
by gritzko 1y ago
Yep, no problem. In place parsing only requires a stack. Stack length is the maximum JSON nesting allowed. I have a C dialect exactly like that.
207.
by gritzko 1y ago
In a world where data centers burn and cables get severed physically, the entire landscape of tradeoffs is different.
208.
by gritzko 1y ago
I recall a WWII sabotage manual that recommends it as a very effective sabotage technique: “let relevant authorities handle it”. Then everyone waits as the relevant authorities have being inquired through proper channels. You can’t even hir
209.
by gritzko 1y ago
I implemented tree based diff for a JSON superset https://github.com/gritzko/go-rdx It boils down to single dimensional, very much like JSON or DOM tree is represented as a linear text.
210.
by gritzko 1y ago
Replicated Data exchange format, RDX. A JSON superset that has diff, patches, branches and merges. Once you have that ability at the data format level, many things become surprisingly straightforward. https://github.com/grit

More ›