3 ms·
Our litmus test was that we invested years into Angular 1.2/1.4, and when 2 came out it was so radically different that we would have had to have effectively le
by erichmond 9y ago
Our litmus test was that we invested years into Angular 1.2/1.4, and when 2 came out it was so radically different that we would have had to have effectively learned a new framework. At that point we switched to React.
Everything you're talking about is great in a vacuum, but stable APIs and backwards compatibility is more important to organizations in the real world.
I can't trust Angular as a framework anymore, as past actions are indicators of future behavior.
- atom-morgan 9y ago> it was so radically different that we would have had to have effectively learned a new framework. At that point we switched to React. Yet the end result was still the same. Another lesson in branding for Angular.
- emodendroket 9y agoI still can't believe they looked at their framework reaching escape velocity and gradually becoming the thing to learn and decided to turn around and announce a backwards-incompatible framework with no migration path that took away two-way binding, the marquee feature that sold everyone on it. Of course they backpedaled on some of that but the damage was done.