3 ms·
I don't like when I can't replace broken part of framework. And this is often the case with angular. Mostly because of foundation it is built on - dirty checkin
by hippich 12y ago
I don't like when I can't replace broken part of framework. And this is often the case with angular. Mostly because of foundation it is built on - dirty checking and it's own dependency injection mechanism. Because of these two there are a lot of things backwards. dirty checking is major cause of whole $digest loop, as well as every async function being mirrored via $-equivalent and non working promises. This cruft accumulates over time and wastes a lot of human resources.
The only reason you might not dislike angular is if you never had to deal with issues above OR you never had different experience, sorry.
- jhall1468 12y agoLike I said, that's a ton of opinion based entirely on YOUR desire to replace parts YOU don't like. Dirty checking isn't perfect (by any stretch) but it's not the worst thing to happen since the cold war either. The bottom line seems to be that your bad experience is relevant while all good experiences are irrelevant because they weren't your bad experience. That tells me you simply don't know how to use it, sorry.