4 ms·
Isn't this comparable to any other situation where you reference something outside a project, even in C with libraries? (I've never used HTMX or even looked b
by fallat 3y ago
Isn't this comparable to any other situation where you reference something outside a project, even in C with libraries?
(I've never used HTMX or even looked beyond this page for it, so maybe what I'm about to say is logically wrong.)
If I said that for an HTMX project you must define all components you use within the project, wouldn't this hx-target example be very easy to identify quickly in the project? You simply grep '#notification-bar' and see where it lives in the project...
I think the goto comparison is somewhat related, because it's about reasoning about control flow (or rather, how it makes it unreasonable) - but isn't this example pretty easy to reason about when you consider you're one search away from finding the notification-bar in the project? You're still creating a tree of components and interactions, and in order for that to happen, you must be able to reference them with confidence in some way.
I still prefer the React way (tree structured components) regardless, but HTMX does seem interesting from a DevX point of view. I think it'll be forgotten about in about 5 years.
- jhp123 3y agoif you decided to write C by building a lot of tiny global functions with no local state that called other globals functions, then it would greatly resemble programming with GOTO.
- michaelcampbell 3y ago> a lot of tiny global functions with no local state that called other globals functions Isn't that Haskell?