Open fabb opened 5 years ago
None of those provide incremental server side rendering as far as I know. The purpose is a bit different too. Those other tools can help with SEO as the entire page is rendered and sent at once to the client. VelociRender is only about performance.
Finally, VelociRender likely requires much less of the developer as it doesn’t require your code to be built in one of those frameworks. Instead it just needs your code to be able to run in JSDom.
Ok this is a good thing to know. So when heavily dependent on SEO, you would not recommend Velocirender?
Google can crawl SPA/Ajax sites now. I’m not sure how or if Velocirender changes that.
It is possible to make Velocirender wait and serve up the entire HTML (but that undos its performance benefits). It might be possible to serve google complete HTML and users the incremental HTML.
I’m not an SEO expert and this hasn’t been designed with that in mind.
I would recommend Velocirender for folks wanting SEO for a SPA app that wasn’t built in one of these other frameworks. It should be much easier to get your app working in velocirender instead of rewriting your app.
I like it a lot when open source frameworks provide comparisons with other similar ones and make it easier for clients to decide on the best fitting framework for the task at hand. There are several mature SSR solutions on the market, like next.js or gatsby, or nuxt. It would be bery nice if you could list similarities and differences to these and other frameworks in the Readme.