In all seriousness though, Cine is pretty nice.

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 yet hype cycles are real and many of them have bellyflopped. Microslop is similarly in real danger of shooting themselves in the foot with this terrible rebranding.

…and your point is?

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.

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.

All good on the wifi front here on Asahi Fedora Linux on Mac mini M1. 😁

(Also worth mentioning the author’s entire modus operandi is to promote Google’s Big Tech vision of AI-all-the-things and hence the blog is chock full of one just-so story after another. It’s quite safe to ignore completely as pure propaganda.)

Every year…every decade…the dream of low-code/no-code emerges once again in another form. And while well-built tools with good UX can indeed help non-programmers build “simple” databases and webpages, this is not something that scales to projects which require programming expertise.

Also the examples in this article make no sense. It’s already trivial to compile plain text in accessible formats like Markdown to beautiful, semantic HTML. You can already build systems which take very simple text descriptions of forms and emit actual forms. Heck, I could take input like:

Contact Me form

name
email (required)
appointment date
message

and turn that into an HTML form with zero LLMs involved. But why even do that? Someone, anyone, could drag’n’drop a form together in a couple minutes. Easy.

LLMs are constantly a (poor) solution in search of a problem. Virtually every just-so story someone can share with me about how an LLM supposedly will solve their problem, I can show examples of how else to do it. We are wasting outrageous amounts of time on technologies unfit for purpose.