3 ms·

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

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)

bestinterest 4y ago
Lots of credit for yourself with htmx, its great. I think I prefer unpoly myself but htmx is winning the popularity because of how vocal you are! I wish the unpoly creator also did similar! Both great frameworks. Hotwire also! I wish there was deeper comparisons on the big three
- recursivedoubts 4y ago
  i always try to mention unpoly unless the discussion is specific to htmx because I agree: it is a wonderful library and henning is a great guy in general. Hotwire probably doesn't need my help, I think dhh has a big enough mic. :)
robertoandred 4y ago
None of htmx's modal examples are accessible, doesn't give me confidence it can be used for serious projects.
- recursivedoubts 4y ago
  if you are willing to jump on the discord, we'd be happy to improve them https://htmx.org/discord https://htmx.org/discord
- benpate 4y ago
  My dude... I made those in like a day, when I was first getting started with htmx. Accessibility has nothing to do with the language or framework you use. It's about the thing you build with it. If you can build it with Javascript, you can build it with htmx. Give this a try, and see if it's any more accessible -- https://benpate.github.io/hyperscript-widgets/modal/ 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.

bestinterest 4y ago

Lots of credit for yourself with htmx, its great. I think I prefer unpoly myself but htmx is winning the popularity because of how vocal you are! I wish the unpoly creator also did similar! Both great frameworks. Hotwire also! I wish there was deeper comparisons on the big three

recursivedoubts 4y ago
i always try to mention unpoly unless the discussion is specific to htmx because I agree: it is a wonderful library and henning is a great guy in general. Hotwire probably doesn't need my help, I think dhh has a big enough mic. :)

robertoandred 4y ago

None of htmx's modal examples are accessible, doesn't give me confidence it can be used for serious projects.

recursivedoubts 4y ago
if you are willing to jump on the discord, we'd be happy to improve them https://htmx.org/discord https://htmx.org/discord
benpate 4y ago
My dude... I made those in like a day, when I was first getting started with htmx. Accessibility has nothing to do with the language or framework you use. It's about the thing you build with it. If you can build it with Javascript, you can build it with htmx. Give this a try, and see if it's any more accessible -- https://benpate.github.io/hyperscript-widgets/modal/ 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.