Thanks. You do make some valid points and would like to pick your brain a bit further :-)
a) What about organisation? Did you feel like it easier to work on a team and share code?
b) Did you had any problems with the compiled code?
Just finished reading the the recently posted No more JS framework[1] and it lead me to this really funny article.
Thought it deserved a top level post.
The EJB part really did make me laugh out loud.
Angular is not that bad. I've used it in one of my major projects and while it wasn't easy to learn all the new concepts, in the end it was well worth it. But like all projects it must evolve and unfortunately that also means adding more complexity and new concepts which will result on a steeper learning curve. It's a risk, but they have to take it.
Thank you Mr Bevacqua for starting this discussion.
This simple, yet powerful default behaviour, is what made start using AngularJS. It has interceptors. But for those not interested in drinking the angular Kool-Aid, your post seems like a a great place to start. Kudos.
@bevacqua
Big fan of your work so will definitely give it a try and keep an eye on it.
Question, how are you planning to keep the cruft out as the library grows. I mean isn't that the problem with jQuery? It just got too big!