thesis: web 1.0 hypermedia-based applications (clunky)
antithesis: web 2.0 SPAs using JSON Data APIs (slick, but complex and & web-native)
synthesis: web 1.5 apps using hypermedia-oriented libraries like htmx or unpoly (slick, web native)
antithesis: web 2.0 SPAs using JSON Data APIs (slick, but complex and & web-native)
synthesis: web 1.5 apps using hypermedia-oriented libraries like htmx or unpoly (slick, web native)
I wish the unpoly creator also did similar! Both great frameworks. Hotwire also!
I wish there was deeper comparisons on the big three
Hotwire probably doesn't need my help, I think dhh has a big enough mic. :)
Give this a try, and see if it's any more accessible -- https://benpate.github.io/hyperscript-widgets/modal/ -- I've learned a bit since those first demos, and have followed every W3C guideline I can find on accessibility to make them.
One more thing, I'm nowhere near being an accessibility expert, so I'm positive someone who knows more will have suggestions on how to improve this, too. But it has nothing to do with htmx/hyperscript, and everything to do with me being new at accessibility.
Bugs/Suggestions/Pull Requests are always welcome. That's what makes htmx fit for "serious projects."
Edited to add: Htmx is a JS-based extension of the natural hypermedia patterns your browser already uses, not a widget library. All of the demos on the site are just that -- demos that show you the kinds of things you can build, and not plug-and-play, ready-for-npm widgets you can just drop into your application without a second thought.