We call this fine-grained hydration and it's made possible by the Tags API which makes it much easier to trace which values are dynamic, where they are used, and where they change. This means Marko can know exactly what code needs to run where whether on the server, in the client, or on both.
I recalled you said Marko was more for MPA's, but by the description of "fine-grained hydration" it sounds like it would work fine for SPAs too? Can someone write an SPA with Marko?
Suppose, for example, one wishes to use custom elements for 3D WebGL rendering, and thinks to use Marko for the template logic and component hierarchy of the application, while the 3D custom elements end up as the leafs in the application markup that do the actual WebGL rendering.
They intend to make a realtime RTS or FP shooter. Will this work out with Marko? How would it differ from choosing Solid.js?
Assume the user only cares about the client side experience, and whether SSR is in place or not doesn't matter much.
I recalled you said Marko was more for MPA's, but by the description of "fine-grained hydration" it sounds like it would work fine for SPAs too? Can someone write an SPA with Marko?
Suppose, for example, one wishes to use custom elements for 3D WebGL rendering, and thinks to use Marko for the template logic and component hierarchy of the application, while the 3D custom elements end up as the leafs in the application markup that do the actual WebGL rendering.
They intend to make a realtime RTS or FP shooter. Will this work out with Marko? How would it differ from choosing Solid.js?
Assume the user only cares about the client side experience, and whether SSR is in place or not doesn't matter much.
(I also see Marko isn't published at custom-elements-everywhere.com yet)