It&#x27;s definitely a risky move as your examples demonstrate, but aren&#x27;t most of the Angular core developers working for Google? I don&#x27;t think they have an interest in generating more consulting work.<p>Angular was arguably the state of the art for a while. I suspect the core team would rather pursue that position again than spend years focusing on legacy support.<p>I&#x27;m not terribly familiar with the perl, php, or python communities, but my understanding is that a lot of the changes made were to &quot;fix&quot; things and &quot;clean up&quot;. Aka, there wasn&#x27;t a &quot;I need this to get my job done&quot; reason to upgrade. On the other hand, client side development has progressed rapidly since Angular 1.0. Things like isomorphic javascript just won&#x27;t work with the old APIs.