The HTML-First Approach: Why htmx and Lightweight Frameworks Are Revolutionizing Web Development
6 points by yawaramin
6 points by yawaramin
> sees title
> sees gray-out
> “AI slop?”
> sees comments
> “AI slop.”
> leaves
AI slop
My work increasingly involves Large Language Models (LLMs), AI-powered systems, and machine learning pipelines for industrial automation, business intelligence, and intelligent applications.
Yup.
Aside from the annoying heading emoji, I didn't notice too many AI-isms in the text. But it's kind of disappointing. I like LLMs, but if I want an LLM's opinion, I'll go ask the LLM directly—whereas when I read someone's blog, it's because I'm interested in that person's perspective.
Was the quoted text originally at the linked page?
I can't see what's quoted – now, or in the earliest capture at https://web.archive.org/web/20251212010014/https://www.danieleteti.it/post/html-first-frameworks-htmx-revolution-en/.
Thanks
What makes you say that?
It is fairly obvious slop. It's hard to describe, people discuss heuristics like em-dashes and overused metaphors and the like, but it's really just in the tone -- if you've seen it enough, you can spot the text smell immediately.
Seeing this on (what used to be) a personal blog makes me realize I need some way to domain-flag sites/links outside of just my search engine. Does anyone have recommendations for a Firefox extension that can do this?
I only picked up the excessive emojis. But maybe I was biased away from thinking it was slop because it used to be a personal blog. And I guess maybe I haven't seen it as much as I think I have... I feel like I have a decent eye for it, but this one wasn't obvious to me.
A lot of emojis, a lot of em dashes, a lot of lists. But also the content of the article is simply bad, it goes into every direction with the most run-of-the-mill explanation for each of them. Like, seriously, the SEO part seems to have been written by someone living 2020.
I don't really agree with the idea that fewer lines is better. For a start, the React example has error handling which seems to be missing entirely in the HTMX example, and secondly the HTMX code seems to have a lot more implicit behaviour - when does the loading message get hidden/displayed? Does the data div get hidden if there's no data?
The React example is more verbose, but the behaviours are all listed there.
Well the React example has implicit behaviours too. You have to remember the rules of hooks. Also there's a fairly famous blog post that dives deep into why even a simple fetch example has a lot more to it than appears at first glance: https://tkdodo.eu/blog/why-you-want-react-query
Regarding the implicit behaviour of the htmx example–it's all encoded in the attributes. Once you learn what they do–which is a one-time cost to learn–you always know going forward, in every htmx invocation you look at, what everything is doing. In this case we know that when the button is clicked, htmx will cause the 'loading' span to become visible only while the request is in flight,_ then hide it again once the request has completed. If there is an error, by default htmx will trigger a DOM event with the details, and then we can have a little JavaScript event listener that handles it.
Who renamed the progressive approach of all life into "islands architecture"? It sounds silly like that