Interesting point of view. We have two worlds now coexisting on the Web and they tend to ignore each other more and more.

Nice recounting of the first meetings to make the web what it is today.

I think this is the right way to look at the problem space. The analysis provides the right pros and cons to look at when picking a frontend framework.

Interesting list. Definitely to keep in mind when developing and deploying a web application.

This is indeed looking more and more like a viable and worthwhile option for web applications.

Nice overview of WebGPU. Also does a decent job laying out the history of graphics APIs. With WebGPU bound to be more widespread and available outside of the browsers things will get very interesting.

Indeed, without deciding to put everything in the public domain, the face of the web would have been very different.

I must resist to redesign my blog I guess... In any case, this is a very nice style for content.

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.

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

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.

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

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

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

This is a big milestone for 3D and computation on GPUs from the browser. I suspect it will have interesting security implications though, we'll see.

This ecosystem suffers from the same warts and doesn't seem to make any progress... lack of transparency, "we know better" mentality, tight coupling, lack of communication. This is especially problematic for something like a browser.

Nice balanced post on the pros and cons of GraphQL.

It's clearly way too reliable. This needs explicit hardening.

Very nice approach to avoid the font bloating on the web. I'm slightly concerned about the maintenance over time but at least it has proper fallbacks and the fonts used seem widespread enough (for now).

A bit of a rant so brace yourselves. Still, it's very much aligned with the current backslash against "everything must be an SPA" trend and makes very good points on how it happened. This indeed turned into a popularity contest based on false premises. Meanwhile... complexity increased dramatically on the web frontend side and the performances are bad for most users.