The difficult path for Vulkan. The data obviously is biased since it includes games and most of them are still targeting Windows and so DirectX. I'd be curious to see something similar excluding games (and so focusing on medical, industrial etc.).

So yes, the climate changed before... now slowly scroll until the end to appreciate how brutal it is this time.

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

The more releases out there the more vulnerabilities are (and could be) discovered. Some actions are necessary to get things under control properly.

Interesting critique of this new platform... it's the beginning of the hype cycle but will probably the same "enshittification" phenomenon than other platforms.

Very nice explanation and metaphors on how CPUs cache levels work.

A good reminder of everything which might go wrong when connectivity is bad. Most tools let you down in such a case.

Definitely a nice Python trick. Fairly elegant, I'll try to remember it.

Packed with useful information. Clearly some things I'm eager to test in there.

Shows well why you likely don't want to use GraphQL. The chances you need the extra complexity and caveats are very slim.

Another good example of how to speed up some Python code with nice gains.

Definitely to keep in mind when using sampling profilers indeed. They're useful, they help to get a starting point in the analysis but they're far from enough to find the root cause of a performance issue.

This definitely shows PyPy as a successful runtime.

Definitely this. In a world where LLM would actually be accurate and would never spit outright crappy code, programmers would still be needed. It'd mean spending less time writing but more time investigating and debugging the produced code.

Interesting research! Is reading code a math and logic task? Is it a language task? Well... it might be its own thing.

The words we use indeed matter. This is definitely a domain where we should avoid ambiguities...

Or why you should let domain simply expire, there's plenty of work to do before that.

Not necessarily my favorite governance model, but if you're on that scheme... those are good guiding principles.

Definitely a complicated history... this doesn't make the evolution or documentation of it easy.

Interesting results. It's especially nice to see how sched-ext allows to easily iterate and experiment with process scheduling strategies.