5 ms·

I completely agree. We are using Angular 1.x at my day job and my team and I are feeling the pain. Manual DOM manipulation compared to React's virtual DOM feels

I completely agree. We are using Angular 1.x at my day job and my team and I are feeling the pain. Manual DOM manipulation compared to React's virtual DOM feels like what it must have used to feel like comparing jQuery to Angular 1. Perhaps frameworks don't rust in the sense that they deteriorate in terms of capabilities over time. But that doesn't mean that they don't become obsolete. Especially when you're building a product and trying to stay competitive, all the while all the the innovation surrounding a framework has packed up and left for a nicer camp.

botskonet 9y ago
We're using Angular 1 too, chosen just over two years ago. The two-way binding/digest nature has really become our enemy. Everything we write has to account for digests and we've wound up with some terribly ugly code to account for digest problems. Angular 1 is great for hobbyists and it makes implementing simple forms easy but when you use it for an enterprise app, it hurts. Our app is still vastly better than decade-old 1.0 we've replaced, but we sure hate the digest now.
- PopsiclePete 9y ago
  >We're using Angular 1 too, chosen just over two years ago. Good god. You chose Angular 1 two years ago? As in 2015? When its horrific shortcomings were already known and the Angular devs were working on Angular 2.x?