3 ms·
It's ironic to see essay about LoB from htmx author who made attribute inheritance as default framework behavior. Basically you can guarantee nothing by looking
by bvrmn 4y ago
It's ironic to see essay about LoB from htmx author who made attribute inheritance as default framework behavior. Basically you can guarantee nothing by looking at piece of htmx code. It can do different things depending on place in DOM tree.
- aaaaaaaaata 4y agoCan you elaborate?
- recursivedoubts 4y agoThat's a valid criticism of htmx and there is a developer who created a conceptual fork of the idea eliminating this design decision: https://github.com/kasta-ua/twinspark-js https://github.com/kasta-ua/twinspark-js I view the issue pragmatically: I think developers should consider LoB strongly when building systems and when using htmx, but I also recognize there are other design considerations (principally DRY). I can definitely see both sides of the argument, however, and would encourage people not to abuse attribute inheritance, just like I would encourage people not to abuse generics in OO languages.