Designing APIs for the Web platform is hard and error-prone. This is why it carries baggage, here is a good example.

I like this idea. It'd be nice if more websites felt like little town squares.

Indeed the trend wasn't new. It's "just" the icing on the cake from the enclosure point of view.

I guess it's time we realise Google doesn't send much traffic on the open web / small web / indie web (call it as you please) and so there's no need to let them harvest.

Indeed, there's no reason to not use .well-known for newer standard files.

This is a good point, unlike what some claims the Internet isn't dying. The commercial crap on top is thinning out and is getting filled with crap indeed. Still, what made the Internet and the Web are still here for people to use.

This piece is strongly worded but the logic is sound. We see many examples of power plays in guise of "innovation" which lead to killing openly sharing (and so killing real innovation). It's urgent to fight back and ensure things stay open.

So many requests based on vanity and hype... I like the question "when you go to other websites do you use it?", we should use it more. Maybe at some point we'll realise that simplicity matters.

This could be a piece full of nostalgia. There is a bit of nostalgia of course, but it's also a path to use what we got in a more valuable and humane way.

Or why I tend to favor desktop applications (made by KDE as much as possible) rather than web applications whenever possible. It's just more pleasant to have things which look and feel homogeneous.

So much this... I'm sick of all those little businesses having only an Instagram or Facebook account or whatever. I wish we'd have proper websites for all of those instead.

Also, it's likely a pessimistic estimate... Indeed, it's mostly based on a list from Kagi, which likely doesn't list many sites which would qualify.

Probably somewhat self serving so the numbers would need to be confirmed with other experiments. That said that case gives a good idea of the price in terms of complexity and resources when choosing to go for an SPA.

There is indeed a path for better support for WebAssembly on the Web platform. Let's just hope it doesn't take a decade to get there.

Another nice resource to discover newer CSS idioms.

This is a very important initiative. For a healthy web platform we need good interoperability between the engines. I'm glad they're doing it again.

I'm not sure I'm quite ready to use this... Still I like the idea, make some noise and have companies turning to those invasive ads to just pay for nothing. The more users the better I guess.

Looks like an interesting tool to check you're doing "everything right" on your blog. That said, it looks like quite a few hoops to jump through. I wish there'd be a way to make all this a bit easier.

Another space with rampant enshittification... No wonder users are jumping between alternatives.

Nice retelling of the story behind WebAssembly.