Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There are techniques for controlling complexity there, and often you can make a single-page react page which will encapsulate complex behaviors.

Often a mix of the two helps. But you end up having one set of code managing the static page, and another for the api-based interactions. and then once you have api-based stuff product asks to add on a feature and a feature until you have mutliple SPAs. :P

Code reuse is a big reason too, why write 10 different SPAs for one site, when you can write 1 SPA with a ton of code/tool re-use.

I always end up taking 1 SPA and make 2-4 different SPAs out of it, each facing a different set of users, with different security/look requirements, but all underpinned by the exact same technology.

So much headaches saved.

Just to make it clear:

- I agree that SPAs didn't come out of developers being idiots, but rather because the shit we had to do before SPAs was craaaaaaaaaaazy. Jesus I remember the old jquery things. And before jquery... shiver...

- I think SPAs are definitely not a one-tool-for-all-problems kind of thing.

- Interestingly enough, SPAs can be a one-tool-for-all-problems kind of thing with SSR, that's what linkedin does. LI is an SPA with the ability to behave like a non-SPA via isomorphism.



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

Search: