"Assuming we have a well qualified need for client side rendering", is the key for me because in most cases there isn't one
"Assuming we have a well qualified need for client side rendering", is the key for me because in most cases there isn't one
All HTML is client side rendered. Is there really a semantic difference between the layout primaries and the data occuring as distinct elements in the payload - especially when that more naturally maps to the origin of the data? We have HTML snippets, why not binding conventions.
I'd argue that it's a better generalisable solution than a thousand client and server implemented templating engines, frankly, because it could be part of the web standard. A page doesn't have to be an interpolation of markup and data contents, that's just one form of it.
Even so, react isn't the best of them joshcollinsworth.com/blog/antiqua...
I have used all of those except quik. They all have compromises, and the ones that get popular all use the same jsx/hooks design as react anyway. That's the thing people think about when they think of react imo - less the framework itself. I like svelte "best", but it's toolchain is less stable.