Sigh. Yet more confirmation that my team has made the correct choice in switching to a mostly vanilla JS development stack (we still use RiotJS for one-way template binding). I was there for the beginning of Angular and it got me hooked on single page applications, but what I am seeing now is the antithesis of productivity. No one building a website for a business should be using this stuff, unless they drank so much…
This is an interesting comment to me because, by essentially building your own framework, that onus is now completely on you. If you want to implement code splitting or tree shaking or whatever, you have to figure that out for yourself. That's time taken away from building product features. Whereas other frameworks can offer this out of the box because smart people in the open source community have figured that all out for you.
In addition, no one coming into your organisation has any continuity of knowledge, so they have to learn all the proprietary ways your app is set up, which is more time lost.