russell

I'm noticing that 5.6 Sol is wired to overengineer and code defensively to a silly degree. Tasks are taking longer to complete, the code it writes is less performant, and I end up redoing more work than before. This is very annoying.

HTTP is a perfectly good protocol if one is trying to use it to Transfer some HyperText, rather than whatever the fuck people actually do with it

POV: Your LLM agent is dividing a by b

My policy of "never eat at Taco Bell" continues to pay enormous dividends.

We should just bring back the em dash Reclaim it for our own

I am excited to announce that we are officially writing a new version of Postgres. In Rust - and creating the LLVM of databases in the process. In the span of a year, we have rewritten SQLite. Keeping the compatibility, increasing its feature set. MVCC, Types, (Live) Materialized Views, among other things. In the process of doing that, we have realized: At the end of the day, what makes SQLite special is that it compiles SQL to a database-specific bytecode. So why can't we compile *Postgres* to the same bytecode? Turns out we can. I ran an experiment called pgmicro as a way to prove this hypothesis, and it works very well. It is time to make this official, and put the weight of Turso behind it. We shall give the world a modern take on Postgres. Wire compatible, but built on a new architecture. We have already heard of others wanting to extend this. MySQL? Redis? the sky is the limit. What can we do if we do for databases what LLVM did for compilers? To prove how powerful the SQLite bytecode is, we are actually running DOOM compiled to the unmodified SQLite instruction set. And because Turso runs natively in the browser, you can play the game in your browser. With the database executing it. Read the full story below! 👇