"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."<p>I wish they'd discuss stuff like this and I wish that MongoDB did not store primary keys on _id field.<p>I blame myself though.
I'm really impressed with Angular.<p>I'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.<p>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.<p>Great work guys!
I've done one project with ember and was very happy with it but I'm now working on a project where I only need parts of the page to be controlled by the framework. So far I'm loving the way angular integrates with the dom but once you get back to the controllers/directives it suddenly feels like I have to do a whole lot more work than with ember. The main difference seems to be that you have to manage updates yourself i.e. use $watch or trigger them yourself by binding to js event. At this point I'm kind of wishing their was an embular project ( :) ) that integrated with the dom the way angular does but had ember's awesome binding/computed properties...
With Javascript disabled the page is completely blank.<p><i>edit (bringing text from comment up a level):</i><p>If you are building apps for people other than yourself, then having a banner to notify them it won't work is better than a blank page.<p>A typical banner that I make includes the following things:<p>- Positioned at the top via CSS and sticks there<p>- Includes a link to <a href="http://www.enable-javascript.com" rel="nofollow">http://www.enable-javascript.com</a><p>- Includes a tracking image so I can see how many people are coming without JS enabled<p>If you have a white page like this blog does, people will think your site is broken and bounce... and may never come back.
We've been using rc versions in production code too. As they've mentioned many times when they say unstable it doesn't mean that it was likely to break, simply that they are free to change the API if they need too.<p>Does anyone know what's the rationale behind the separation of ngRoute? It's less than 4KB and less than 2KB when gzipped. I don't think it's worth the "pain" of having to remember to add another source file.
Great timing. The angular based project I've been working on for the past 6 months just had a soft launch the other day. Being able to tell the powers that be that we are no longer on the unstable branch will ease a few minds.
Nice guys! I've been tracking the rc's with Ionic Framework (<a href="http://ionicframework.com/" rel="nofollow">http://ionicframework.com/</a>) and just updated to the final. I've especially loved ngAnimate and ngTouch which have been really solid.
I 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!).<p>Also looking forward to seeing new Angular features being worked on again!
I just wrote a yeoman generator to bootstrap a phonegap application with angular 1.2.0 : <a href="https://github.com/dsimard/generator-angular-phonegap" rel="nofollow">https://github.com/dsimard/generator-angular-phonegap</a>