AngularJS 1.2.0: timely-delivery
blog.angularjs.org
AngularJS 1.2.0: timely-delivery
1–10 of 64 posts
Re: AngularJS 1.2.0: timely-delivery
#2Re: AngularJS 1.2.0: timely-delivery
#3I've previously worked with Backbone.js, and found that many things in Backbone where I've had to manually develop are readily available in Angular.
Moving from Backbone to Angular has made the code much cleaner, and smaller in size. Whereas in Backbone, the code slowly became a mess with all the event listening and event triggering (probably my fault), in Angular, that has all been abstracted for the most part.
Great work guys!
Re: AngularJS 1.2.0: timely-delivery
#4Re: AngularJS 1.2.0: timely-delivery
#5Re: AngularJS 1.2.0: timely-delivery
#6Also looking forward to seeing new Angular features being worked on again!
Re: AngularJS 1.2.0: timely-delivery
#7I wish they'd discuss stuff like this and I wish that MongoDB did not store primary keys on _id field.
I blame myself though.
Re: AngularJS 1.2.0: timely-delivery
#8I noticed that Angular was likely to release this morning since all the issues for the milestone was finally cleared out - looking forward to moving to 1.2 stable from 1.2 rc2 (we're using rc2 in production code!). Also looking forward to seeing new Angular features being worked on again!
Re: AngularJS 1.2.0: timely-delivery
#9Re: AngularJS 1.2.0: timely-delivery
#10"This commit introduces the notion of "private" properties (properties whose names begin and/or end with an underscore) on the scope chain. These properties will not be available to Angular expressions." I wish they'd discuss stuff like this and I wish that MongoDB did not store primary keys on _id field. I blame myself though.
It is also clear from the discussion that there are dissenting opinions -- we are constantly iterating and welcome issues and pull requests to make features work even better. The best way to influence AngularJS is to send a pull request.