3 ms·
This is definitely in the same vein as http://boringtechnology.club/ http://boringtechnology.club/ After several years of drinking the client-side kool-aid, I'v
by MattyRad 7y ago
This is definitely in the same vein as http://boringtechnology.club/ http://boringtechnology.club/ After several years of drinking the client-side kool-aid, I've come to realize that it almost never has a positive ROI. On top of the false premise that it "makes pages faster", it doubles the cost of the entire pipeline/stack, it doubles the amount of documentation that needs to be read/written, and it doubles the statefulness of the app, amongst other things. Maybe under the best conditions by the most knowledgeable devs, client side apps could be impressive, but your typical company doesn't have those resources.
- cottsak 7y agoThere's such an "ego load" associated with this investment too. I find that even when a developer comes to realise that the SPA mess is largely unjustified, they're rarely willing to admit or change anything.
- MattyRad 7y agoAgreed. It's very much a sunk cost/escalation of commitment fallacy. https://en.m.wikipedia.org/wiki/Escalation_of_commitment https://en.m.wikipedia.org/wiki/Escalation_of_commitment Also bad is that junior engineers see shoddy client side code and internalize it. As an example, one junior engineer asked me how he was supposed to iterate over an array server side when I told him he didn't need to use Vue on a page. Server-side rendering fixtures had been completely forgotten. I accept my responsibility in causing this mess though. I niavely pushed the SPA on my myself, my coworkers, and our end users years ago and have to live with that sin daily.
- cottsak 7y agoThat must be humbling. Props for identifying it and adjusting course tho.