indygreg.bsky.social
indygreg.bsky.social
@indygreg.bsky.social
California requires all deaths on property within 3 years to be disclosed. Deaths beyond 3 years may be considered “material” if they are noteworthy (such as a murder, fire, or something reported in media) and usually disclosed. It’s hard to miss this on the interview the sellers complete!
November 6, 2025 at 7:06 AM
Regarding Mach-O signatures, my open source Apple code signing tool has support for diffing binaries and the signature data in them. Please make noise in GitHub if there’s features that could make validating reproducible binaries easier. gregoryszorc.com/docs/apple-c...
Apple Code Signing — Apple Codesign 0.29.0 documentation
gregoryszorc.com
October 30, 2025 at 2:36 AM
Flying back to USA Saturday afternoon. Just a quick visit to Amsterdam to bookend my trip.
October 23, 2025 at 7:08 PM
I think PRs came into existence because they were simply the easiest thing to technically implement on clients and servers using vanilla Git. Push a branch and diff it. What I don’t understand is why GitHub never innovated beyond that.
October 21, 2025 at 4:17 PM
Reposted by indygreg.bsky.social
definitely the funniest form of this: I hated autoconf so wrote rust's configure in "plain posix sh" like with shell functions etc. a bunch of that got cribbed to rustup's sh bootstrap which has then been cribbed _everywhere_ like uv and lean's boostrap and whatever, the code totally escaped the lab
May 14, 2025 at 6:57 AM
They used equal visual spacing between the widest point of the glyph - often the serif. This is comical - sans any sense of design aesthetic.
May 4, 2025 at 7:50 PM
Did you see the Python tail call interpreter write-up? Apparently modern LLVM is smart enough to emit the optimal assembly without use of computed goto. No clue if that would translate to Rust though. blog.nelhage.com/post/cpython...
Performance of the Python 3.14 tail-call interpreter
A deep dive into the performance of Python 3.14's tail-call interpreter: How the performance results were confounded by an LLVM regression, the surprising complexity of compiling interpreter loops, an...
blog.nelhage.com
March 16, 2025 at 9:20 PM
The regression fix didn’t make it to LLVM 20.1.0. But I spent a few hours this weekend getting a 20.1.0 build with the patch and python-build-standalone using the new toolchain.

Performance testing is hard.
March 10, 2025 at 5:39 AM

If you look at tools like github.com/google/go-licenses, they look for well known files (e.g. LICENSE) and perform text similarity to discern the license.

You’d think the tooling would support advertising an SPDX identifier like nearly everything else in 2025. Nope!
GitHub - google/go-licenses: A lightweight tool to report on the licenses used by a Go package and its dependencies. Highlight! Versioned external URL to licenses can be found at the same time.
A lightweight tool to report on the licenses used by a Go package and its dependencies. Highlight! Versioned external URL to licenses can be found at the same time. - google/go-licenses
github.com
January 20, 2025 at 12:29 AM