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