I think we should make it possible to opt-in to the legacy strategy.
I know the whole point of velocirender is incremental rendering, but I think there is a big, awesome use-case we are ignoring with being able to SSR any SPA (any framework or style), and that with an Http2 boost in a faas could be a very strong draw to velocirender.
Currently, you have to trade any SEO wins you get from SSR to use velocirender, but what if incremental-rendering was optional. You could pull in more people that way and then let them choose if they have the right use case to prioritize the speed boost velocirender provides over the otherSSR benefits.
Picture this scenario:
netlify offers faas for their static-sites to offer a little extra juice static-sites need. What if velocirender could be used to easily with minimal effort add SSR to their SPA app? That would be awesome.
I don't know how much work offering legacy strategy as an opt-in would be, but considering it's the fallback for browsers that don't support the features we need for incremental-rendering, I would think it shouldn't be too much effort.
I think we should make it possible to opt-in to the legacy strategy.
I know the whole point of velocirender is incremental rendering, but I think there is a big, awesome use-case we are ignoring with being able to SSR any SPA (any framework or style), and that with an Http2 boost in a faas could be a very strong draw to velocirender.
Currently, you have to trade any SEO wins you get from SSR to use velocirender, but what if incremental-rendering was optional. You could pull in more people that way and then let them choose if they have the right use case to prioritize the speed boost velocirender provides over the otherSSR benefits.
Picture this scenario: netlify offers faas for their static-sites to offer a little extra juice static-sites need. What if velocirender could be used to easily with minimal effort add SSR to their SPA app? That would be awesome.
I don't know how much work offering legacy strategy as an opt-in would be, but considering it's the fallback for browsers that don't support the features we need for incremental-rendering, I would think it shouldn't be too much effort.