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 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.

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.

Good reminder that links are the soul of the world wide web!

There's the carbon footprint but of course there's also the water consumption... and with increased droughts this will become more and more of a problem.

This is definitely something to keep in mind and check if you have any LUKS encrypted storage. The key might be less protected than you think.

This is impressive results. Clearly much less artifacts than on previous such models.

Plenty of good advises for dealing with text in interfaces. It's a bit too much focused on phone and watch for my taste glancing over challenges specific to larger form factors. Still this can be useful to keep in mind.

Good milestone for this project I've been using for a long while now.

Looks like a nice reference about WebGPU. Unsurprisingly it covers some 3D basics as well.

Interesting approach to get a better understanding and awareness of your surroundings as a tech lead or lead dev.

This is a good thing that Google makes such a move. Still, it could be so much more. Tidelift still seems to be the best offer for securing your dependencies.

Nice tool for monitoring how processes use the GPU.