I completely agree, and I’ve said as much. meta tags + RSS is all your blog needs.

Ah I see. Well it’s true that there’s some concern about how the compatibility story could work from M3 onward, but as I said, M1/M2 generation is pretty solid and you can get a great deal from the used market. I don’t know who was telling you it sucked. 😅

A used Apple M2 desktop or laptop is probably the best deal in the biz right now. I’m rocking Asahi GNOME on an old Mac mini M1 right now, works great. Why worry about ditching Asahi? Are you having any problems with it?

The downsizings will continue until morale improves.

I’ve been sharing this far and wide today, and bookmarked as a must-have resource. Absolutely fantastic article, with reams of modern best practices. Love to see it!

This is getting really old, really damn fast. 🫩

I suppose nobody should work with you then, since you’re here complaining about things publicly.

Hehe, I’m actually using a 6 year-old Mac mini M1 running Asahi Fedora, and it kicks ass.

Pagefind is an awesome solution and can work with pretty much any static site generator. https://pagefind.app/

For example, I use it here on my site That HTML Blog.

XML is very good for documents and other structured content formats. The problem is people took XML and used that for things that aren’t really documents. That led to a lot of people hating XML for the things it wasn’t good at and thus hating XML even for the things it is good at.

I wish we could find a reasonable middle ground. I’d love to have a job where I work a lot more with XML to be honest!

Just sounds like somebody who isn’t good at their job. “Not committing to answers” isn’t the role, the opposite is true.

And why is this article so antagonistic? The takeaway is…what, exactly? It’s obvious to anyone who’s been paying attention for the last few years that most companies working in tech desperately need UX—good, caring, talented people working in UX who are given real decision-making power. Otherwise the people making decisions are user-hostile FOMO VPs and C-suite types, and they’re making a damn mess everywhere.

The answer to bad UX designers isn’t no UX designers, it’s better UX designers. And give them some damn power already!

I’m a big fan of Web Awesome. It can scale from just a CSS starter like Pico all the way to a full component library, depending on what you need.

https://webawesome.com/

…and your point is?

I’m in this meme, and I don’t like it. 😄

You can use Islands Architecture combined with Pjax-style page loading techniques so you specifically don’t deal with full-page HTML reloads, although the honest truth is now that we have cross-page View Transitions, combined with in-browser caching those “reloads” can actually appear to perform in a fast and pleasing manner even more than janky old-school SPA techniques.

Blockchain.

'Nuff said. 😂

There are a lot of good points here, but the content farm-y vibe of the post is really distracting me. I’d rather read a blog of someone simply sharing something they’ve built with htmx and the pros vs. cons they encountered in the process. (I like htmx a lot, I just haven’t gotten a chance to use it in a production project yet!)

Unfortunately, a lot of browsers now completely obfuscate themselves and don’t put anything unique in the user agent string. They intentionally don’t want to be detected at all beyond “I’m a modern browser”.

That’s literally what the OP said they didn’t want to do. Did you read it? 😄

Huge, huge fan of this API. Can’t wait until we don’t need a polyfill anymore. The built-in commands concept is cool and hopefully will expand in time, but the custom commands functionality is a real game-changer! Anything which makes wiring up various web components into a real UI more declarative and web-native is most welcome.