This is a good piece. Killing all planning is indeed not a good thing. Setting plans in stone wasn't a good thing either, it's no reason to go to the other extreme.

Or why browser monoculture is bound to become more and more of an issue. Sad to see Mozilla's weak response to this move. Can't bite the hand that feeds I guess.

Well... that didn't last long before such disgusting behaviors appeared there. Now will companies seriously tackle the issues? Or will it be the same joke as content moderation on Facebook?

Since the tooling is still far from great for web frontend memory analysis, it's nice to see some effort there.

And that's why I find hard to swallow that "microservices" is the go to answer from lots of people nowadays when you discuss architecture. There are interesting promises on paper but that requires you to ignore several layers of complexity. It's likely fine to get there at some point, but bake in all that complexity from the start? I don't think so.

Interesting benchmarks on HTTP/3. Clearly fares best at long distances.

Now that looks like a really nice CSS framework. I like the approach with a very limited set of classes and pushing you to focus on semantic.

Interesting research on how relying on digital systems reshape our memory and our perception of our own abilities.

The never ending question of how to monetize open source...

Nice tip about Java collections. Didn't know you could collect streams that way, definitely handy.

As expected, realtime rendering is now getting extremely close to photorealistic.

Interesting thinking about going beyond what's strictly needed for a task.

This is good to see this is still making progress.

Take a solution in search of a problem, add strong monetary incentives for using the solution, mix the whole with magical thinking and... you get the blockchain fad.

Using MySQL or MariaDB in production? Think again.

Looks like a nice resource for home automation. Sending SMS is indeed a nice and simple notification system.

I think this applies more largely to any evolving language or ecosystem. You rarely can know such a thing in full and if you do it's only at a given point in time for a few given contexts. Only path to expertise in our field is practicing in various contexts and staying up to date as much as humanly possible.

Good reminder on why mypy is an essential mitigation to use when dealing with Python. This avoids some quite common mistakes.

This is a good way to get into how Javascript engines try to optimize the code thrown at them. It's definitely not an easy job with Javascript...

Despite the problems with Mozilla's politics and funding, this is the main reason why I use Firefox as my main browser (even on my smartphone). We can't have a monopoly on which organization influence the web standards... unfortunately we get fairly close from that position.