Lots of good stuff definitely coming. This should definitely help make it more approachable to lots of people.

People are putting LLM related feature out there too hastily for my taste. At least they should keep in mind the security and safety implications.

Interesting point. As the memory safety of our APIs will increase, can we reduce the amount of sandboxing we need? This will never remove completely the need if only for logic bugs, but surely we could become more strategic about it.

Interesting, it confirms garbage collectors can be the source of unrecoverable performance degradation in request based systems.

This is a very important distinction to keep in mind. It's one of those source of bad mistakes in C++.

This would definitely be a nice change to the Java language.

It's nice to see progress coming to lifetime checks in C++ compilers.

Definitely not as fashionable as the kubernetes craze. This gives very interesting properties that multi-tenant applications can't really provide. The article is nice as it lays out properly the pros and cons, helps make the choice depending on the context.

The cleanup of that mess is still on-going. A bit more automation would help.

Definitely this. C++ isn't going away anytime soon. Rewrites won't be worth it in important cases, so improving the safety of the language matters.

A nice zine introducing the topic of faults and failures in distributed systems.

Another cruel reminder that basic reasoning is not to be expected from LLMs. Here is a quote from the conclusion of the paper which makes it clear:
"We think that observations made in our study should serve as strong reminder that current SOTA
LLMs are not capable of sound, consistent reasoning, as shown here by their breakdown on even such a simple task as the presented AIW problem, and enabling such reasoning is still subject of basic research. This should be also a strong warning against overblown claims for such models beyond being basic research artifacts to serve as problem solvers in various real world settings, which are often made by different commercial entities in attempt to position their models as a strong mature product for end-users. [...] Observed breakdown of basic reasoning capabilities, coupled with such public claims (which are also based on standardized benchmarks), present an inherent safety problem. Models with insufficient basic reasoning are inherently unsafe, as they will produce wrong decisions in various important scenarios that do require intact reasoning."

Interesting use of cryptography without a security concern. It's more about safety and ensuring something wasn't missed by mistake.

On the importance of invariants and consistent requirements in our trade. Admittedly it's a long demonstration but it show the point well.

Excellent piece from Herb Sutter once again. This is a very well balanced view about language safety and how far C++ could go in this direction. This is a nice call to action, would like to see quite some of that happen.

Check out the docs branch for detailed explanations. This exhibits a loop hole in the Rust compiler allowing to break lifetime inference... and from there all the usual guarantees go through the window.

It's here to sell something. That said it does a good job explaining the Erlang model and its "let it crash" approach to failures. Also highlights the obvious limitations.

Very interesting contribution to the FreeBSD hackers mailing list. Gives quite a good background about Rust, C++ and safety. Debunks a few claims you can easily hear in many places as if they were common knowledge.

The results of this investigation are actually super scary... Even if you don't own one, those are in our streets. In any case it is a clear statement that you can't and shall not run an automotive company like a startup...

Very interesting musing about undefined behaviors and language constraints. This is a bit Rust focused for obvious reasons but is also looking at what other languages have been doing.