3 ms·
Some years ago, a bright guy created something called 7 GUIs. It’s a collection of seven problems that all UI systems must successfully implement, and it was in
by danielvaughn 4y ago
Some years ago, a bright guy created something called 7 GUIs. It’s a collection of seven problems that all UI systems must successfully implement, and it was intended to act as a guide for comparisons.
Unfortunately I think the author has passed away, but it would be interesting to see it rekindled and used for baseline comparisons like these.
https://eugenkiss.github.io/7guis/ https://eugenkiss.github.io/7guis/
- deleted 4y ago[deleted]
- edflsafoiewq 4y agoI don't think Htmx is a good fit for those. I wouldn't want a server roundtrip for any of them (except maybe part of CRUD).
- DannyPage 4y agoHyperscript[1] pairs well with HTMX (as it should, it’s by the same group) and would fill those gaps. [1] https://hyperscript.org/ https://hyperscript.org/
- xutopia 4y agoWhat are the advantages of Hyperscript over plain old Javascript?
- recursivedoubts 4y agoa few: - it is designed to be embedded directly in HTML - it can listen for any event (unlike on* attributes) - it has native support for CSS selectors: https://hyperscript.org/docs/#dom-literals https://hyperscript.org/docs/#dom-literals - it has async-transparency: https://hyperscript.org/docs/#async https://hyperscript.org/docs/#async - subjectively, it is easier to read than JavaScript, particularly for the short, light scripts it is designed for (toggling a class, etc.): `on click toggle .clicked on me` hyperscript is more of a glue language than something I would recommend building an entire application out of (although people are doing that!)
- tomhallett 4y agoWow, this is very cool! I think this applies not only to gui frameworks (react vs htmx), but also to design systems (bootstrap, tailwind ui, etc).