There are many more useful codes than are generally used. We shouldn't shy away from using them when it makes sense, it also means the client side must be ready for them. Very often client code makes wrong assumptions on the possible codes.

Nice exploration of false sharing on performances in several hardware scenarii. A couple of surprises along the way.

OK definitely surprising research. Some of the results are interesting. Clearly it shows a high level of socializing with those birds.

Interesting train of thoughts. Indeed we should keep in mind that large scale software is almost always a complex adaptative system, even more so if we don't forget the people developing it and not just focusing on the code. This can give us guidelines on how to organize the development.

Also does a good recap about what a complex system is and how it behaves. Definitely worth a read at least for this.

Definitely complicated to identify and resolve paths on this platform. I had to deal with it from time to time and this can definitely turn into a pain in the neck.

Are we surprised? Not at all... this is an ethical problem, this is a legal risk. The alternatives will hopefully know better.

This is really a huge update. Brings in lots of features which were clearly missing.

Very good advice: stop, status, selection, focus, finish, next. If it feels like "stop starting and start finishing", it's probably no surprise.

Shouldn't come as a surprise if you paid attention to C++ evolutions for the past 30 years. We're now reaping the fruits though, so it's really become easy to keep both options in sight when designing. This is especially important for performance sensitive code.

Nothing really new here (apart from the "how easy it is these days!")... Still it needs to be reminded on a regular basis. :-)

OK, this is a pre-print so to take with a truckload of salt. If further nice results get built up on this it could turn out interesting though. This is a much more intellectually satisfying approach than the current arm race of "let's throw bigger models at the problem". This has the potentially of reducing the computational complexity of those models, this is definitely welcome in term of energy and hardware requirements. Let's wait and see...

This was only a matter of time. It'll be interesting to see how this will unfold. Potentially it could turn into lawsuit cases being built up, it could also mean content producers get a cut down the line... of course could be both. Since FOSS code also ends up in training those models I'm even wondering if that could lead to money going back to the authors. We'll see where that goes.

Interesting tool... this is generally done with tools where you're captured into a GUI. Moving this to text and static generation opens the door to proper versioning etc.

Very nice resource if you wondered about the journey to space.

Very interesting trick, definitely something worth doing if you want to host something at home and keep the power consumption low.

This is indeed one of my favorite tools. Of course, I use it a bit less nowadays... still, I should have written this letter.

I actually always wondered about this, now I know. :-)

Interesting way to look at the problem, definitely thought provoking.

Nice post explaining the common algorithms used for load balancing. Each having their own trade offs of course. Well done with tiny simulations.

Definitely this! Major FOSS projects should think twice before giving their street creds to such closed systems. They've been produced with dubious ethics and copyright practices and since they're usable only through APIs the induced vendor lock-in will be strong.

Looks like a funny tool to generate music.