Server-side rendering has always been React's painful little side thorn. In part, it's because React's existence aims to do one thing and do it well - render stuff quickly and efficiently without giving developers too much of a headache.
While the ideas behind React is great, it also proved to be its Achilles heel - especially when it comes to SEO.
Bots and crawlers have a thing against single page apps.
It's fine if you're just using React to build the app portion.
Waiting for anything is the bane of efficiency. This is why SPAs struggle with SEO in general because while crawlers are generally patient, there is a thing called a 'crawl budget'. At some point, your crawler is going to give up on your SPA and move on to something else.
This is why there is a resurgence in discussions about SSR - or server-side rendering.
What is server-side rendering?
Think your old school, processed on the server and you get an actual HTML document back kind of set up. But it's not that black and white - and this article explains it quite well.
This 4-part history of the web series also maps out how we got to where we are now.
📌 What I'm reading
This week, I started reading Tools of Titans as I find myself getting bored of the usual flow of productivity and motivation content that's recycled ad-nauseam in my feed.
I've seen the title floating around for years but never picked it up until now.
The quick flip-through verdict is this: it's not your typical, feel-good productivity motivation content. It's raw, real, and to the point - summarized into bite-sized interview-esque recaps of people that's done and achieved something.
Overall, I'm liking it since it vibes well with my current state of jumping around content to keep learning and entertained.