As a community, we've seen enough untyped PHP spaghetti code in the early 2000s and never want to go back there.
As a community, we've seen enough untyped PHP spaghetti code in the early 2000s and never want to go back there.
https://spectrum.ieee.org/media-library/a-3d-illustration-sh...
It's very common to have a CMS feeding images to an LLM that extracts the contents and gives image files a meaningful file name and alt tag.
[1] "Don’t Be Ugly By Accident!": https://gwern.net/doc/psychology/okcupid/dontbeuglybyacciden... (mirror)
Why is the content changing between refreshes not "(helpfully) bookmarkable"?
The HN front page (ie. "page 1") does that but it's a very useful bookmark.
You bookmark a link to the directory so you don't forget the directory's entry URL.
The use case the author is talking about is a different one: You are configuring a complex item in a shop, and want to bookmark the URL so you can save it, recall it later, share this configuration with someone, or compare it with a different URL.
In this case, you also would expect little details to change (pricing, descriptions, photos) but the structure of the state should stay the same.
It's very frustrating when you share a link to a product detail page, only to discover that all your filters and configurations have been lost.
Be it React or Svelte or whatever. With serverless backend if you want to keep costs down. Although a server from Hetzner isn't that expensive and you can host multiple APIs there.
That's the whole point of HTMX: Going back to what works: trusty old HTML attributes, but giving them intuitive interactions.
Instead of learning the microframework du jour, you just add some attributes into your HTML templates, and get your desired result.
> This isn't X, this is Y
This is ChatGPT's favorite rhetorical flourish without exception.