3 ms·
> 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
by 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.