4 ms·
6. Pre-rendering is a complete mess. Yes, if you try to pre-render Hello World application it will do fine. But in real world examples your main menu, for examp
by romanovcode 8y ago
6. Pre-rendering is a complete mess. Yes, if you try to pre-render Hello World application it will do fine. But in real world examples your main menu, for example needs to pre-render only the top links and not deep-links. Good luck doing that kind of stuff in Angular or React. Also Express on-premise pre-rendering of dynamic pages is terribly slow, 2 seconds to load an website if you have serious application.
- bestest 8y agoIt looks like you are either misguided or are doing something wrong. This is not how React or Angular (or Express) works. Only the stuff that is required per-route (or whatever state) is "rendered" server-side. The rest is chunked away and retrieved when needed. From my experience, express rendered react apps never take longer than php / whatever rendered sites, given the data dependencies are retrieved from the same source (api, db e.g.).
- romanovcode 8y ago> Only the stuff that is required per-route (or whatever state) is "rendered" server-side Yes, the whole page, which includes the header, footer, menus etc.. What's your point here? I don't get it.
- bestest 8y agoCorrect. The whole page is rendered on the server. The way it would be rendered by a PHP script. There is no need to pre-render anything else, it's a SPA. The concept of pre-rendering is usually redundant in the context of SPAs.