Ah OK, thanks for your reply.
Wasn't sure what you meant by "bringing together".
I assumed you were meaning to connect both, not replace.
Fair though.
I'm wondering whether the next big thing in this space is going to be more BE-driven and include streaming larger fragments or some other sort of improvement.
Anything that does more than Alpine and htmx so far seems to struggle bringing innovation.
It was fun once working on a Laravel project where it was somdtimes confusing for a new collaborator to make sense of which "x-attributes" were Alpine, so client-JS-related and which ones were part of server-side Blade templates, so dynamic but not "reactive".
This naming collision was preventable and misleading, but it somehow still "felt right".
Wasn't sure what you meant by "bringing together".
I assumed you were meaning to connect both, not replace.
Fair though.
I'm wondering whether the next big thing in this space is going to be more BE-driven and include streaming larger fragments or some other sort of improvement.
Anything that does more than Alpine and htmx so far seems to struggle bringing innovation.
It was fun once working on a Laravel project where it was somdtimes confusing for a new collaborator to make sense of which "x-attributes" were Alpine, so client-JS-related and which ones were part of server-side Blade templates, so dynamic but not "reactive".
This naming collision was preventable and misleading, but it somehow still "felt right".