GPUI (v0.2.0), the GPU-accelerated Rust UI framework that powers Zed, is on crates dot io. 👀 crates.io/crates/gpui

"your database doesn't have checksums?"

This is definitely true in my experience with databases as well yes, that includes me too xD

Nothing comes close to the Postgres extensions ecosystem. Kinda insane that people have extended it with features you just can’t pull off with other databases: •Full-text search like Elasticsearch •Message queuing like RabbitMQ (and kinda Kafka like) •Job / task schedulers

I guess I am done with the book!

After my Accord fun project using Claude Code I decided to do a similar hard (maybe impossible?) new project with OpenAI Codex to see what happens. Here’s the project plan for Bifrost. github.com/kellabyte/bifr… Fuses TursoDB & DuckDB storage for atomic OLTP+OLAP writes.

[PVLDB] Enhancing Transaction Processing through Indirection Skipping vldb.org/pvldb/vol18/p4… Whereas VMCache improve pointer swizzing's complexity by removing the swizzling, this work points out that page and frame hints are highly effective, and okay if they're wrong.

Please check out our paper on checking “observational correctness of database systems”. Its first line of work as far as I know that checks both SQL semantic as well as consistency correctness of databases. Really enjoyed working on this problem. dl.acm.org/doi/10.1145/37…

Arguably, Go doesn't have asserts because, well, Pike doesn't like them 🥲

I really like the way "Why Programs Fail" book frames this: - A defect is a programming error. - The defect can become infectious, putting unrelated components in bad state. - Software fails when there's critical bad state. Assertions are a great way to contain the infections.

hi, i'm v! indian, a blr-based dev looking for more frens in the systems & vc community :) a lil about my background: > i like to talk about databases > i work at a database company > i like databases > i'd like to learn more about databases & systems programming i stay some

I designed and built (with a great team) a very large scale one of these ‘database per resource’ designs just over a decade ago. They have a ton of nice properties (low blast radius, great scalability), but also introduce a lot of complexity (e.g. finding the right database).

Apparently designing a Notion / Figma-style system is a super common system design interview question. My fren, who’s been grinding backend interviews, read this post. I explained the architecture, and bro lost his mind when I told him it handles a billion writes per second.

It's a horror story, a funny one, because "legacy" databases don't come with guard rails. The kind that stop you from accidentally nuking your entire production database at 2:17 am. The simplest solution is to run queries wrapped in a transaction. However, people don't do it for