Both Datastar and HTMX have the same issue: they want to pretend to be HTML. So they force themselves into writing several DSLs like this to pretend that this is still "just HTML".
Since they have a full "Datastar expression" language, I'd just expand that. Then you wouldn't need these weird constructs:
Both Datastar and HTMX have the same issue: they want to pretend to be HTML. So they force themselves into writing several DSLs like this to pretend that this is still "just HTML".
Since they have a full "Datastar expression" language, I'd just expand that. Then you wouldn't need these weird constructs:
Well they are both "just HTML", Datastar being better about being spec compliant using the dataset attributes and all.
By expanding the "Datastar expression" language, do you mean a compiled language or moving all the expressions into JS files or something else?
> By expanding the "Datastar expression" language, do you mean a compiled language or moving all the expressions into JS files or something else?
Doesn't matter. They literally already have a Javascript-like DSL: https://data-star.dev/guide/datastar_expressions
Datastar is spec compliant HTML. Please point me to the code that's not HTML spec compliant