Maybe there’s a case to be made for a theme setting on a screen somewhere. Or as others have said, this could be set at the browser level per site.

I just think having a toggle up in the header is sort of a UX waste.

Yes. Toggles are unnecessary, a phenomenon of weird nerds. Just match the system settings and you’re fine.

Either this is a poorly written article or it is totally LLM slop.

Developers bragged about scale and beauty, and the brag couldn’t be faked; the artifact proved it. Skill was the visible half of a pair. Taste rode along with skill.

huh?

What will the LLMs do when all the humans whose work they have stolen in order to function at all decide to leave the marketplace of ideas? 🤔

My shorter answer: if you think you need to use canvas,

you don’t.

(Unless you’re literally building a drawing app.)

99.99% of web applications would be better off virtually ignoring “best practices” introduced by Big Tech.

Just go look at the repo. 😅

Well that’s just demonstrably wrong. Go look at the commit history of the go port. Extensive use of Copilot. Slop.

And it was slop coded by engineers who think it’s fine to talk in abusive mannerisms to chatbots inside of GitHub PRs.

I’m staying far, far away from this nonsense. Personally I only write in JavaScript anyway and only use tsc for type checking. Will pin to v6 for as long as humanly possible.

DOA.

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

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!

Overhyped then.

Overhyped now.

Stop trying to make “API economy” happen! 😂

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

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/

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