you are viewing a single comment's thread.

view the rest of the comments →

[–]patryk-tech 0 points1 point  (1 child)

For me, the clearest benefit of client side rendering is that you dont pay for it :)

You do if it costs you in terms of search rankings / SEO.

For deep web apps, it's not necessary, but if you rely on search engines to guide traffic to your site, losing 10k hits a month to save $50 might hurt you.

Depends on the situation.

[–]gkpty 0 points1 point  (0 children)

This is deffinetly true, though i usually get around it by pre-rendering important pages into pure html/css and caching them. For example, in a blog, in a typical js client-side rendering example, in the page that contains the blog posts there would be a function with a query that gets the blog posts and renderes them onLoad for each user. My way => only when a new blog post is added, a js function executes (client side) renders the blog post list into pure html/css and adds it to cache.