> Is it discouraged to use server-side rendering? No, it's not! But it's discouraged to use it as the only rendering layer. Server side rendering has its unbe

> Is it discouraged to use server-side rendering? No, it's not! But it's discouraged to use it as the only rendering layer. Server side rendering has its unbeatable advantages - speed. That's why you can view content on https://huu.la https://huu.la within second, similar methods are used by Google, Twitter, etc. A lot of people might say, we have faster networks now. Believe me, even at Bay Area, it takes time to, first, download your powerful client-side library, second, bootstrap your powerful client-side app, and third, call XHRs to fetch your data. Not to mention there are so many mobiles, with even less capable networks. So from my experience developing Huula, I would recommend using a combined approach. For places where speed is critical, for example your landing page, help page, use server side rendering; for places where a lot of user interactions will happen, use client-side rendering since it gives your more support for componentization if that's a word and user interactions.