Viewing profile — atombender

Maybe not the most discussed author on HN, but still thought I would post. John Crowley was a rare breed among American writers in that he was an accomplished science fiction and f…

This is a while back, and we've since re-engineered it a bit, but we had database shards processing 400-500 rows/sec, maybe more. Vacuum was not able to keep up even with more aggr…

My secret is paprika powder. It changes the whole flavor profile. A fair amount is needed, and it needs to be pretty fresh powder, not something that's sat in the cupboard for two …

Not true, unfortunately. The dead tuple build-up can happen in a very short amount of time. I speak from having had to deal with this in a production environment that used the SKIP…

A performance pitfall that isn't addressed in the DBOS article at all is the bloat problem: If you update or delete rows that you consume, dead tuples start to accumulate due to Po…

https://archive.ph/zxECq

No, but when the compiler isn't enforcing anything, how do you know which ones are safe and which ones are not? If we ignore declarations etc. and only consider statement lines tha…

That is explicitly referenced in the article.

The original Zig code is metaphorically one big unsafe block. Even if the Rust port is made up of 3% unsafe blocks, that still means 97% of the original Zig code has been made safe…

This library is based in part on that same paper.

> Project Hail Mary was predominantly practical effects Don't drink the Kool Aid. The studios love to make this sort of claim — recent examples include F1: The Movie, Top Gun: Mave…

Anyone know what he actually did at Google? Was it an active role, did he publish anything interesting? Or was it more of an Institute for Advanced Study kind of position?

https://archive.is/wtC7m

He's also recently been on Empire [1], the Goalhanger podcast — and sister show to the great The Rest is History (which I hope will cover this period someday, though they tend not …

Counterpoint: All of the current Postgres codebase is already wrapped in an invisible unsafe{}. The difference with a Rust codebase like this is that all of the unsafe code has bee…

People bring this up a lot. What I see here is that thousands of potentially (not actually, just potentially) safety risks have been neatly tagged in the code. If you took a progra…

For those struggling to find tech specs: Apparently [1] it has a 2MP CMOS sensor, F2.4 aperture, 24mm equivalent wide-angle lens, and shoots a resolution of 1920x1080. [1] https://…

My memory is fuzzy here, so I may be wrong. But I remember the generation of buggy WYSIWYG editors that preceded ProseMirror, and they were all contenteditable-based. They would ty…

While these use contenteditable, it's not accurate to say they're just contenteditable plus some UI and interop. None of these modern editors (Wordgard, ProseMirror, Lexical, Slate…