Hacker News new | past | comments | ask | show | jobs | submit login

In many cases SSR is automatically better, including the ones you're talking about, because page rendering errors get thrown in an environment you have more control over, as well as faster devices rendering your already fast pages even faster. In my experience, enterprise work stations are clunky abominations, and if you can save someone some ram and battery why not? It also gives you a platform for building other kinds of non-gated apps that inherit the same benefits.

You might think you have control over the environment someone accesses the app in, but you don't, at least not entirely, and why not just make it as easy as possible to get their work done however they want?

Of course, this doesn't make your thing automatically better all around. That's a design and implementation problem. But you do potentially help everyone by starting at the bottom




Round trip to the server to compose your HTML feels less responsive. Else you could just do it in PHP anyway.


Surely you wouldn't just be server side rendering though. Nobody needs a page load for every route change necessarily. These are implementation details.


> you could just do it in PHP

That's two languages: javascript and php. Many frontend developers would prefer to just work with one — javascript.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: