3 ms·
> Then SPAs take away what they give because they are error-prone and costly to develop. So much state to track. There really is something in knowing that even
by locallost 5y ago
> Then SPAs take away what they give because they are error-prone and costly to develop. So much state to track.
There really is something in knowing that even if you screw up somewhere it will all be gone by the next click. I mean, of course the job is difficult precisely because there are a lot of details to track, but what if you actually shouldn't if you don't really need to? I work on a product that definitely does not need to, and the amount of time we spend of bug fixing compared to our pre-SPA days is mind boggling. So we can spend a lot of time on making ourselves better developers, which is good in general, but do we need to if our product is really simple?
- cottsak 5y agoYet very few teams/devs/leads push back on the SPA spiral of death
- locallost 5y agoBecause it's the thing you have to do to be professionally respected these days. And respect is won not by the customers, but by your peers. Having 10 colleagues think you're good is more important than 300k customers thinking your product solves their problems. It's backwards, but understandable because the tech people think normal users don't know what's important because they don't understand tech. But that's also backwards because tech is there to be used by the people for something useful.