Interesting trick in Java internals which is especially improving map lookups.

Nice little article. It's a good way to point out that aiming for the lowest Big-O approach is often not what you want in terms of performance. Always keep the context in mind, and in doubt measure.

This is indeed a nice tool to explore and check the memory layout of data structures.

Nice little comparison of raw loops and ranges in C++. As always, measure before making assumptions... Unsurprisingly it ends up on the usual readability vs performance debate.

Looks like a nice resource to get better at finding the root cause of performance regressions and optimising code.

Interesting reasons to let go of Rust, some spaces indeed can have a safety vs performance tradeoff which would justify using good old C.

Nice performance comparison of file handling in multithreaded context. It's surprising how slow MacOS seems to be there.

It could be so much better indeed. Unfortunately in great part this is about UX design and carrying heavyweight frontend frameworks though...

Looks like an interesting DSL to write high performance Python code.

It shows unexpected results in its measurements. It also highlights the importance of proper settings for your database system.

Nice exploration of JIT based techniques in Python.

Nice primer on the impact of too many branches in your code on the CPU. This is sometimes a good way to boost performance when you're mindful about that.

It becomes clear that there are more and more reasons to move back to simpler times regarding the handling of web frontends.

More studies needed to confirm this, it is a single data point. Still it looks like Rust could take the HPC world by storm once it gets a better GPGPU story (still early days there).

Or why you shouldn't insert an abstraction just for the sake of it. Also clearly not all abstractions are created equal.

A good reason to use more modern C++20 APIs for parsing code.

Excellent piece which shows why React (or Angular) is almost always a bad choice and that you'd be better off banking on the underlying web platform. It leads to better user experience full stop. The article also goes in great length debunking the claims which keep React dominant.

OK, the numbers are indeed impressive. And it's API is fully compatible apparently, looks like a good replacement if you got Pandas code around.

Nice paper which debunks the choice of the language as an important factor for energy efficiency. The previous papers had a too simple model, this one puts forth a more complete causal model. There are many factors at play regarding energy efficiency, the programming language itself is not really one of them.

Data layout is essential for performance reasons. It is too often overlooked. If you want real speed you need to help the memory subsystem.