3 ms·
I'm still firmly of the opinion that nobody wants a SPA apart from the developers of that app. I'd bet any of us could find a ton of weird and unintuitive thin
by mattmanser 8y ago
I'm still firmly of the opinion that nobody wants a SPA apart from the developers of that app.
I'd bet any of us could find a ton of weird and unintuitive things your app does, as well as it probably being slow to load, hard to use and brittle, in that you'll regularly put out an update that inexplicably breaks something for a day or two.
Add on top that massive extra expense of doing a pure SPA compared to the ease and simplicity of developing a mixed server/front side app, I have no idea why anyone sane ever signs off on a SPA.
And that's before we even get onto the vastly better tooling and development environments that server-side languages have.
- sam0x17 8y agoIt could be that our app is uniquely situated to avoid these issues, but we have had the opposite experience. Our API is versioned so things never get out of sync, the frontend code has no external dependencies so its as unbrittle as one could imagine, and we use aws API gateway to fake server side endpoints, so we dont have to do some weird url scheme. This could never work with a CRM though.
- c-smile 8y agoI've architected Web Application that runs as in a) connected as in b) occasionally disconnected mode (LocalStorage + sync when online). For #b SPA is the only option.
- pdimitar 8y agoNobody is saying that SPAs using modern web technologies -- like offline mode -- do not have any use. The problem is that SPAs are shoehorned on many places where they are absolutely not necessary and only complicate things.
- sam0x17 8y agoTo me SPA = no server side page generation + an API server. Maybe I use the term too generally.