4 ms·
You need to ask yourself if you need a website or a web app. Sometimes your project can be split into both. The homepage, login, billing, privacy policy, and ot
by s_y_n_t_a_x 7y ago
You need to ask yourself if you need a website or a web app.
Sometimes your project can be split into both. The homepage, login, billing, privacy policy, and other static pages can be a traditional server-side rendered website. More complex sections, like a file browser or text messenger, can be apps.
- vorpalhex 7y agoWhy do you need server-side rendering for static pages? They are static pages - let them be static html and send the file. Pages like that get millions of times more reads than writes.
- ape4 7y agoOften "static" pages aren't 100% static. It might display the user's login name, etc.
- s_y_n_t_a_x 7y agoServer or build time rendered. I shouldn't have specified. It's up to the situation.
- wil421 7y agoOr make the parts of the app(s) with tabular or news feed type data be more of a SPA type. I find SPA tolerable when they are apps users are filtering, posting, or manipulating data. Once you make my back button weird or break URLs I hate SPAs.
- deergomoo 7y ago> Once you make my back button weird or break URLs I hate SPAs. The silly thing is, it’s very easy to not do that. It wouldn’t surprise me to learn that a lot of what people hate about SPAs is down to so many people doing a bloody awful job of building them.