Indeed, the C++ syntax for closure captures is way superior to the Rust one. Interesting musing on a potential path forward for Rust.

Indeed, in most case you don't need the extra complexity. Also interesting is showing that even if the application has to scale rapidly you still got quite some time to plan the transition to something else. It makes Postgres a sane default choice.

Maybe we have a path forward for performance stackful coroutine? More pieces need to fall in place but this looks promising.

Interesting to see how it behaves in practice when passing parameters by value. Turns out there are surprising patterns in the data.

Definitely this. It's a good reminder of the boy scout rule. It's fine to clean up as you go and when you find the opportunity.

A good way to see the basics of computer vision. This gives all the building blocks needed.

Nice explanation of the very early steps leading to the kernel loading.

A good reminder that you don't always need a full blown forge.

A good introduction at the early steps when a process is started. Covers what happens in the kernel, the ELF interpreter and your language runtime before the main function is called.

Indeed, WebDAV is too easily overlooked nowadays although it's a respectable protocol with general availability. It's likely available somewhere in what you already use.

An interesting set of principles for code reviews.

I'm happy to see I'm actually very much aligned with one of the "Attention Is All You Need" co-authors. The current industry trend of "just scale the transformer architecture" is indeed stifling innovation and actual research. That said I find ironic that he talks about freedom to explore... well this is what public labs used to be about, but we decided to drastically reduce their funding and replace that with competition between startups. It's no surprise we have very myopic views on problems.

Interesting notes about borrow checking in Rust. Looks like it does a good job exploring the whole space of issues one can encounter with potential solutions.

Interested in how dithering works? All the algorithms you will ever need are probably on this list.

A long paper which explains what can be expressed with concepts in C++.

This is a very valid question. The most likely answer is somewhat cruel though.

Indeed it feels like the Rust community has a cultural problem around abstractions. In a way it feels similar to the one Java developed years ago. This can bring lots of complexity and obfuscation you don't want in your project.

If it fails for everyone then it's not a bad choice on your part, right?

Bunch of random script ideas. Some I don't see the point of for me, some are neat and seem useful.

It was around two years ago, but maybe a good idea to revisit it with the recent AWS outage?