Deep dive on a proper benchmarking and implementation for 1M task on the Erlang runtime. Clearly the previous benchmark had room for improvements.

Nice piece which shows how easy it is to get such models to produce nonsense.

A good reminder that Flatpak is no silver bullet. It's a bit of a rant at times still it has some good points in particular the security implications are not always properly conveyed to the users. Some thinking might be required regarding what's lost compared to "traditional" packaging approaches.

Very interesting case full of lessons. Of course, increasing the complexity of the system overall can lead to such hard to find issues. It's also a tale into how seemingly innocuous settings can interact in unexpected ways. I also like the lessons learn pointing to the fact that you can and should debug even the systems you use through abstractions, diving into the code is almost always a good thing (even if in this particular case it wasn't strictly necessary in the end). And last but not least it shows the tension between mastery and automation... the more you automate the least you master the system, and at the same time this automation is necessary for building resilience in the system.

There's a new grep alternative in town. Looks really fast and has an interesting interactive mode. Definitely something to check out.

Looks like a very powerful tool for debugging and analyzing processes involving a Python interpreter.

OK, that looks like an interesting idea for the frontend bits if your stack is mainly Python based. Still very young though.

Probably the best analysis of the new Apple device I've seen so far. Focuses more on the design of the user experience and compares with the strategy behind other similar devices. There are likely a lesson or two to be drawn from it.

Celery is a popular solution for job queues in the Python world... it's far from perfect though. This list of fixes to make it safer to use is welcome if you're stuck with it.

Interesting post, highlights why it's better when languages are designed in a more community fashion (make sure to read until the conclusion). At least in term of popularity it seems to help.

This will hopefully solve most of the oddities in the generic types syntax of Python. Will be available with CPython 3.12 and will need support from type checkers of course.

Nothing really new but well written. This highlights fairly well the importance of decomposing projects, having at least the broad strokes of the architecture laid down and how automated tests help drive the progress. It's nice to see it all put together.

Nice and thorough workshop on vectorization, where it comes from, what it can do and how you can write code which is easier to vectorize for the compiler.

Interesting idea, for sure on a complex enough system just managing the dependencies can quickly become a full time job.

This rings true to me. What a messy path to get better at our craft!

This is looking like a bad move. Clearly the fault of western countries though which let things unfold ambiguously regarding copyright... Now Japan is weakening copyright for everyone.

So close... and still. This is clearly still in the uncanny valley department at times.

This is a good point, this is a quality before quantity type of problem.

This looks like a move in the right direction regarding desktop portals on Linux.

Interesting way to list all the data stores of your system and map them. Has the advantage of being very lean and simple to apply.