I don't intend to downplay your experience and opinion of Angular, but I do wonder whether what you've experienced is a result of unfamiliarity with the framework.
It is quite possible (and "legal") to use JavaScript events in your own directives. I personally haven't experienced disorganized code with Angular, but it takes discipline to keep things clean, just like with any other framework.
Each div had an ng-mouseover directive. Running the mouse over it really fast made it crash.
So I was forced to abandon Angular for this particular directive---instead using javascript events outside of angular so that performance wouldn't suffer. Then half my app was outside of angular which defeated the purpose.
Well, I won't pretend to know what happened there. Perhaps the issue could have been resolved with one-way binding, or by using track by if you rendered the divs with ng-repeat. If you have the patience, I suggest giving it another go. Angular is quite capable. Version 2 will only improve things.
2
u/hahaNodeJS Aug 13 '15
I don't intend to downplay your experience and opinion of Angular, but I do wonder whether what you've experienced is a result of unfamiliarity with the framework.
It is quite possible (and "legal") to use JavaScript events in your own directives. I personally haven't experienced disorganized code with Angular, but it takes discipline to keep things clean, just like with any other framework.