gomponents-htmx VS twinspark-js

I've built www.gomponents.com for stuff like this and, in my not so humble opinion, it works great. I've got an HTMX extension for it as well: https://github.com/maragudk/gomponents-htmx

I now always use https://github.com/maragudk/gomponents for frontend components (I'm the author of that library) together with HTMX (https://github.com/maragudk/gomponents-htmx), and it's just so much more fun and fast to work with.

That'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

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.