So there was a measurable problem (large bundle size) that they sought out to fix (in addition to upfront loading time). The first thing to do would have been t

So there was a measurable problem (large bundle size) that they sought out to fix (in addition to upfront loading time). The first thing to do would have been to _not_ engage in SSR, or Angular 2, or any other big architectural change without first checking if actually properly slimming the bundle would have helped first. Next, how do you proceed till almost ship without actually solving one of the core initial problems you set out to fix? Before porting the universe, it seems like you should at least remove that risk or convince yourself you know how to do it. I'm going to go on a limb and also completely disagree with the conclusion that a React rewrite was the right thing to do. My experience is that engineer morale isn't maintained by staying in framework and rework hell - instead, morale increases when engineers have opportunities to deliver high-value experiences to users. Not shipping is a common and understandable reason for engineers to leave, and if your employees are hankering to leave because the tech they use isn't the current flavor-of-the-month, you may need to reassess your cultural values screened during the hiring process.