3 ms·
Another angle I'd like to add to this discussion is something that gets near zero attention: longevity. Many SPA developers rapidly move from project to projec
by fleddr 6y ago
Another angle I'd like to add to this discussion is something that gets near zero attention: longevity.
Many SPA developers rapidly move from project to project. Every once in a while, they learn yet another JS framework, and then hop between jobs to use that.
They never look back. They never truly need to take responsibility for a tech choice.
Try to hire an Angular 1 developer to work on 300K lines of code today. You can't. No skilled front-end developer would take on such a job with options to work on hotter tech.
Any SPA choice you make today will be completely obsolete in 3-5 years. 3-5 years, or even 10 years or more, is a normal life cycle for a serious web property. And not just obsolete, you'd have the hardest time getting the tool chain to still work at all.
The original developers don't care, they using tech N+5 now, somewhere else. They'll be very vocal how N+5 is vastly better than anything else, and really the only option for "the modern web".
- eximius 6y agoThis is just the COBOL problem in newer clothes. Raise the pay and someone will decide it's worth their time.
- fleddr 6y agoSure, but timelines are different. Angular becomes a front-end COBOL in just a few years, not 3 or 4 decades. There's more. A typical front-end architecture depends on a complex interwoven tool chain with a lifespan of at best years, sometimes even months. Same for modules. It's normalized to have an absurd dependency tree of hundreds to thousands of inter-depending modules. The vast majority of which will be abandoned in a few years.