4 ms·
I love this. I've seen a lot of similar "use HTML as HTML" type things recently (probably a lot coming from the HATEOAS crowd). I'm not a web developer, and I
by benrutter 3y ago
I love this. I've seen a lot of similar "use HTML as HTML" type things recently (probably a lot coming from the HATEOAS crowd).
I'm not a web developer, and I really don't understand how we've ended up in this state where:
- web starts as a means to share documents, HTML is built around that
- eventually people want to build general applications (a la google docs) so they build tools that let you build non-document things by pretending they're documents
- everyone thinks those tools are great and starts using them
- 90% of the web is still documents, but now its all built in frameworks where you build a non-document by pretending its a document, even though in actuality, we're normally just building a document in the first place.
The whole thing is a batshit crazy mess and I don't understand how as a global engineering culture we view it as anything other than completely insane.
- nosefurhairdo 3y agoHATEOAS = Hypermedia as the Engine of Application State (in case this saves a search). The JavaScript tools for building web applications are nice when used correctly. I can't imagine the product I work on would be easier to build with HTMX, but perhaps I'm ignorant. I wonder though, are there more enjoyable, non-web UI engines out there? Given that web app UI was glued together on top of a document sharing platform, it makes me think native UI dev should be more coherent.
- tracerbulletx 3y agoThe platform isn't that much of a mess imo. I think if you look at individual web application code bases they're kind of a mess because the penalty for doing it wrong isn't that high compared to real physical engineering just throwing the business thing in without planning actually does have a higher ROI. If anything the 30 year old legacy code bases are still much worse than the typical React application and services tangle you get today.