Hey Hashnode!
I'm a developer and I've been working on client-side SPAs for the last two years. I recently decided to change my job and I'm doing research on what technologies to focus next to sharpen my skills.
I'm used to working on web apps with separated repositories, React on the front-end and Node/Go on the back-end. However it seems like server-side rendering got popular and so I decided to take a look at the current landscape with popular boilerplates and so on. The end result of SSR looks really promising but the process itself feels a bit convoluted to me.
If the industry is moving towards SSR, I'm fine with learning it but if the client-side still has a good market share, I'd like to stay there for a while until React with SSR matures.
I'd be glad if some people could share their experiences so I can understand the current landscape.
Nishant Agrwal
I would say server-side vs. client-side rendering in React is not an either-or choice. SSR is usually used as a first-load optimization technique, while leveraging the same client side code (mostly). You can't go wrong learning React today. If you feel like page load is too long, you can look into how to optimize it using SSR.