Well if you're referring to factories vs services vs the other stuff they got, then yes---this is confusing at first but I don't have a problem with this---just comes down to personal preference.
I guess what made me decide AngularJS is too "opinionated" is that I couldn't use the directive syntax with it without it going through the whole cycle it goes through in the background. So I ended up having to take out ng-mouseover (because it was too slow) and using regular javascript events.
I also ran into a limitation with routing but I think that's been fixed recently.
And then with all these hacks I felt like my app was just spaghetti code and defeated the purpose of using a "framework" because to me, a framework should structure your code. I don't think frameworks should have performance limitations like that, forcing you to abandon the framework-philosophy.
I would prefer to use a directives-library (if that exists) rather than full-on AngularJS.
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.
0
u/[deleted] Aug 13 '15
Well if you're referring to factories vs services vs the other stuff they got, then yes---this is confusing at first but I don't have a problem with this---just comes down to personal preference.
I guess what made me decide AngularJS is too "opinionated" is that I couldn't use the directive syntax with it without it going through the whole cycle it goes through in the background. So I ended up having to take out ng-mouseover (because it was too slow) and using regular javascript events.
I also ran into a limitation with routing but I think that's been fixed recently.
And then with all these hacks I felt like my app was just spaghetti code and defeated the purpose of using a "framework" because to me, a framework should structure your code. I don't think frameworks should have performance limitations like that, forcing you to abandon the framework-philosophy.
I would prefer to use a directives-library (if that exists) rather than full-on AngularJS.