gavinhoward

140 ms·

1.
by gavinhoward 1mo ago
This is the first time I've heard a use for LLMs that I think might be good.
2.
by gavinhoward 3mo ago
> Looks like operational transforms to me. Sort of. I add provenance, which helps properly identify collisions, and require a well-defined order by stacking [1] changelists. > The doc claims it's the first with this technique. Mo
3.
by gavinhoward 3mo ago
The best answer I have is for you to read the "History Model" section of that design doc through the "Implementing CRDTs" subsection.
4.
by gavinhoward 3mo ago
When it comes to large assets, wasting large chunks of space is a problem. If your chunks are 64 kib average (from the Lore document), but changes only average 1 kib (which could be a high estimate), then you will still run out of space 64
5.
by gavinhoward 3mo ago
As someone who has thought a lot about VCS design [1] [2], the chunking approach is the wrong one and will still waste space. [1]: https://gavinhoward.com/uploads/designs/yore.md [2]: My WIP VCS has been named Yor
6.
by gavinhoward 5mo ago
Because Git was faster. This mattered because speed is the killer feature [1], and speed is often seen by users as a proxy for reliability [2]. [1]: https://bdickason.com/posts/speed-is-the-killer-feature/ [2]: h
7.
by gavinhoward 6mo ago
> At this point if your VCS isn't a layer above git plumbing, nobody gonna waste time using it. Probably true, but it's a shame because there are better ways of storing and processing the data, ways that natively handle binar
8.
by gavinhoward 6mo ago
Okay, but if you combine the curried and tuple styles, and add a dash of runtime function pointers, you can solve the expression problem. [1] [1]: https://gavinhoward.com/2025/04/how-i-solved-the-expression-...
9.
by gavinhoward 6mo ago
Bram Cohen is awesome, but this feels a little bare. I've put much more thought into version control ([1]), including the use of CRDTs (search for "# History Model" and read through the "Implementing CRDTs" section)
10.
by gavinhoward 9mo ago
> For instance, you might think that big tech engineers are being deliberately demoralized as part of an anti-labor strategy to prevent them from unionizing, which is nuts. Tech companies are simply not set up to engage in these kind of
11.
by gavinhoward 9mo ago
I have had to put programming aside in 2025, probably for the rest of my life, so 2026 will be the year I reskill and reinvent myself. But most importantly, I want to finally become as kind, patient, and charitable as I have always wanted t
12.
Piecemeal Formal Verification: Cloudflare, Java Exceptions, and Rust Mutexes(gavinhoward.com)
2 points by gavinhoward 9mo ago|0 comments
13.
Use the Mikado Method to do safe changes in a complex codebase(understandlegacycode.com)
4 points by gavinhoward 9mo ago|0 comments
14.
by gavinhoward 10mo ago
Hey, where can I apply to a job like yours? I may not be smart enough, but I may be. And I am very interested in formal verification.
15.
by gavinhoward 10mo ago
SAMS does do that. Read my article carefully; it also requires modification and distribution rights for users. See principles 0 and 1.
16.
by gavinhoward 10mo ago
The title of the blog post downplays the absolute masterclass that this post is. It should be called "A Tale of Four Fuzzers: Best Practices for Advanced Fuzzing." And if you don't have time, just go to the bullet point list
17.
by gavinhoward 10mo ago
https://gavinhoward.com/2023/12/is-source-available-really-t...
18.
Redundancy vs. dependencies: which is worse?(yosefk.com)
3 points by gavinhoward 10mo ago|0 comments
19.
BC Maintenance Terms(github.com)
3 points by gavinhoward 1y ago|1 comments
20.
by gavinhoward 1y ago
I hope that FOSS work is never a burden, but that's too idealistic. For some, FOSS work is a burden on them and their loved ones. To those for whom it is, please don't feel obligated to continue. I haven't, and I made this
21.
by gavinhoward 1y ago
One of the few times I've read a paper before it was posted. I like this paper. While it's not anything groundbreaking or sensational, it did help me with the design of something I am working on.
22.
by gavinhoward 1y ago
> It has been mentioned that it’s possible that the default for debug builds is that every single function is compiled as an async function. I.e. there is canonically only one function color. But then, for those that choose to only use b
23.
by gavinhoward 1y ago
From my experience, the calling convention was, in 0.9.x, just an implementation detail, until it wasn't. I think I may still reserve judgment for when async is fully implemented. Then I'll torture it again.
24.
by gavinhoward 1y ago
As the author of a semi-famous post about how Zig has function colors [1], I decided to read up on this. I see that blocking I/O is an option: > The most basic implementation of `Io` is one that maps to blocking I/O operations.
25.
Fsyncgate: Errors on Fsync Are Unrecovarable(danluu.com)
1 points by gavinhoward 1y ago|0 comments
26.
by gavinhoward 1y ago
This looks excellent. I will probably implement this model for my own language.
27.
Formal Methods Let You Explore the Corners (2016)(johndcook.com)
3 points by gavinhoward 1y ago|0 comments
28.
by gavinhoward 1y ago
I like this split much better. Someone else drew the line at marketing capacity, [1] which is also a good one. [1]: https://old.reddit.com/r/programming/comments/1kwpeeq/the_tw...
29.
The Line of Death(textslashplain.com)
3 points by gavinhoward 1y ago|0 comments
30.
I Solved the Expression Problem(gavinhoward.com)
3 points by gavinhoward 1y ago|0 comments

More ›