4 ms·
There are cases where a SPA might be a good idea, I think those cases can be counted on one hand. I don’t mean the products, but use cases. I could imagine it
by mosselman 8y ago
There are cases where a SPA might be a good idea, I think those cases can be counted on one hand. I don’t mean the products, but use cases.
I could imagine it would be more complex to build Slack using traditional server-side rendered HTML than building it as an SPA.
Nowadays though you see blogs, CRM systems, etc being built as SPAs, which just makes it more complex to work on them.
- MaxBarraclough 8y agoSPA blogs? So the individual posts don't have their own URLs?
- rogual 8y agoOne example is the Ludum Dare site (ldjam.com). They migrated from Wordpress to a custom blog which I would call a SPA. It loads posts from JSON and won't render anything without Javascript.
- fuzzy2 8y agoA good SPA uses `pushState` and URL routing to have individual URLs for views.
- qwerty456127 8y agoFeeling enthusiastic about SPAs in general can't stop me from saying this souds like a horrible, fundamentally pervert idea.
- mosselman 8y agoDon't ask me, I am not the inventor of such advanced technology ;). Apparently there is some benefit to server-side rendering of blog posts.
- notyourday 8y agoI'm pretty sure that's the only place where SPA ( or MPA ) aren't a solution in search of a problem is a site/application that needs distributed compute due to a number of requests it receives in a short amount of time.
- senorjazz 8y agofor webapps they are great. However most websites are not webapps and are not needed. A page that is basically just text, a webpage equivalent of a magazine page does not need to be SPA - yet usually is sigh
- mosselman 8y ago'Webapp' is not a narrow enough use case. 'Chat app' would be more of the depth I am talking about and even there you can easily build a basic chat application using server-side rendering and smidgins of javascript to add new messages to a <div>. Generally I would say that SPA are overkill.