10 up and 1 down, posted by ponyfoo 1330 days ago 12 comments
Another well written article :)
What now is wrong about client-side rendering?
Hash routing? It's obsolete anyway. Speed? Client-side rendering can be (and often is) faster than server-side rendering. The only reason we still do server-side rendering, on the other hand, is because of SEO — and that roadblock is about to disappear as well.
You've got it all backwards. Why do you think twitter went into full client-side rendering and then back to shared rendering? SEO? Lol.
Client-side rendering is never faster than server-side rendering for first load. It just can't be. I can't believe I have to point this out to people.
Nobody is disputing that client-side rendering is great after first load. But that doesn't mean you can get away not doing server-side rendering on first load.
It does depend on the use case. If you have a website that requires authentication, you can load the whole code while the user logs in. In that case, SEO is not an issue either already now.
It also does depend on your market. Certainly there are some markets where you might have to eek out every last bit of reduced latency. But if your market is a country where nobody has a connection of less than 10MB/s on their desktop OR phone then you can have a 1MB codebase plus stylesheets compressed to ~500KB and served by SPDY/HTTP2 downloaded, decompressed and running in less than 250ms. Why would you then ever go through the additional work of rendering on the server?
Interesting and do you have proof that client-side rendering is faster?
It is a great pity to see that folks who have commented on your blog and are at all critical have had their comments deleted.
Even my comment
"A number of comments have been deleted, why is that?"
With a reply from bevacqua "Because they didn't bring anything to the discussion besides "fuck you, you are wrong"
AFAIC they definitely added to the discussion by raising opposing points of view and balance which is of interest to me.
I firmly believe that comments that are on topic and not slanderous etc. should never be deleted from any blog.
Seriously? Response for that page is 200 OK with no content.
Clear your cache, there was a caching bug a while back and it must've bitten you :)
Oh wow, it was one very persistent cookie apparently. I've cleared cache a few times already and restarted browser and everything, but now that I removed all the .ponyfoo.com cookies, it started to work again. Phew. Thanks for the tip. :)
yeah I made the mistake of thinking browsers would honor the "must-revalidate" cache-control directive