Angular Blog

Dart is doing fine inside Google. It is used by extremely important projects, like, for example Adwords. These teams are very happy with it and have no intention of changing. Brad Green already posted a follow-up post on the omission of Dart on his slides: http://angularjs.blogspot.dk/2017/04/official-languages-at-google.html (I work on Dart.)

"Angular 1" is now known as Angular.js and is effectively at the end of its line. Angular 2+ is now simply Angular. All new releases follow a naming of version X.Y.Z where X indicates breaking changes, Y non-breaking new features, and Z is bug fixes. Version 3 is being skipped over due to poor naming of the related Angular Router lib. http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-going-to-b…

The banned version is the 1.5.8. Could the following announce be related? Angular 1.6 - Expression Sandbox Removal: https://angularjs.blogspot.mx/2016/09/angular-16-expression-sandbox-re…

Try http://angularjs.blogspot.de/?hl=en If that doesn't work, try a private tab so that it doesn't use any previously-set cookies: Firefox: ctrl-shift-p Chrome: ctrl-shift-n

I wonder, does the .co.uk one also redirect to .de? You might find that as an already-"localised" one it doesn't redirect? http://angularjs.blogspot.co.uk/

Did you see the blog post from last week on Angular's efforts to help developers transition from 1 to 2? http://angularjs.blogspot.com/2015/08/angular-1-and-angular-2-coexiste… As for little/no benefits, that is certainly not true. Angular 2 is going to be better in almost every way from Angular 1 and there are many great apps built off Angular 1. If you haven't tried Angular 2, I suggest giving it a go once the they get to beta.

The Angular team listened to the community and has been working on an upgrade path. I found this blog post useful in convincing my team that we are not going to be wasting time as long as we continue to follow angular and JS best practices: http://angularjs.blogspot.com/2015/08/angular-1-and-angular-2-coexiste…

No blog post yet (should be at http://angularjs.blogspot.ca/), but you can read the changelog here: * https://github.com/angular/angular.js/blob/v1.4.0/CHANGELOG.md

> Is there any differentiation between the two on API stability? Compare http://angularjs.blogspot.co.il/2014/10/ng-europe-angular-13-and-beyon… > Our goal with Angular 2 is to make the best possible set of tools for building web apps not constrained by maintaining backwards compatibility with existing APIs vs https://github.com/emberjs/rfcs/pull/15 > This is not a big-bang rewrite; we will continue development on the master branch, and roll out changes incrementally on the 1.x release train. The 2.0.0 release will simply remove features that have been deprecated between now and then. Our goal is that you can move your Ember app to 2.0 incrementally, one sprint at a time.

I don't know exactly how many of the Durandal & Angular convergence[1] features made it into Angular 2.0, but it looks like lazy module loading and a better component syntax did, which is fantastic [1] http://angularjs.blogspot.fi/2014/04/angular-and-durandal-converge.htm…

Since we are yet to see the first Angular2 release (almost there, but not yet); most Angular2 third-party resources may not provide the most up to date information, so the best place to learn Angular right now is really the official Angular documentation i.e. https://angular.io/ , because it is updated quite often. 1. If you are looking for a book to learn in a sequential way then ng-book is a good option. ng-book is updated regularly however it is not free. https://www.ng-book.com/2/#features 2. New blog posts are also a great way to learn about certain Angular topics. Examples: 2(a): http://blog.thoughtram.io/categories/angular-2/ 2(b): http://angularjs.blogspot.com/ (Has both Angular 1.x and 2.x articles, written by Angular core developers) 3. Learning by observing: 3(a): material2 is a library, being developed by the Angular team itself, that is based on Angular2 and is frequently updated to use the latest Angular2 version (currently RC5). I refer to the material2 source code to learn the best way to write my own Angular2 app and custom components: https://github.com/angular/material2/tree/master/src/lib

It was in order to keep with SEMVER. Everything Angular was version 2 except for Angular Router, which was version 3. So the team decided to make the next major version 4 to keep them all aligned. http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-going-to-b…

They had a router package in angular 2 which had 3 as it major version number. To sync all version numbers, they decided the next version would be 4. http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-going-to-b…

Angular 2 to Angular 4 is not a good example of getting comfortable using something then the next version coming out. They are the same framework and it is trivial to upgrade Angular 2 to Angular 4. "Updating to 4 is as easy as updating your Angular dependencies to the latest version, and double checking if you want animations. This will work for most use cases." from https://angularjs.blogspot.com/2017/03/angular-400-now-available.html Angular 1 to Angular 2/4 is a valid argument though.

Angular 2+ is just Angular. Angular 1.x is AngularJs. If you are trying to differentiate the two in google, add -AngularJS to the end of the search. Also pretty good bet you're going to want to search within the last year for up to date posts. Versioning and Releasing Angular http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-going-to-b…

Most developers should be able to simply update their dependencies and rebuild. A few APIs have been deprecated, but they continue to exist and can be removed at a developer's leisure, per our versioning policy [0] http://angularjs.blogspot.com/2016/10/versioning-and-releasing-angular…

PS: oh, i guess i missed this, the next major angular overhaul will have to come with a full rebranding: http://angularjs.blogspot.de/2016/12/ok-let-me-explain-its-going-to-be…

The issue with Angular in extensions has to do with the fact it uses eval on the page DOM, which is controlled by the webpage. The webpage can put code into the DOM, and then let Angular execute it from within the higher-privileged extension. Angular <1.6 had a sandbox feature which blacklisted specific attacks like this, but was not a general solution and was specifically not intended as a security feature. They entirely removed the sandbox in 1.6 because people kept thinking it was a security feature: http://angularjs.blogspot.com/2016/09/angular-16-expression-sandbox-re… I'm not going to fault someone for not reporting a specific vulnerability with a specifically not-security feature that has already been removed.

FYI: Oct. 8 release by the Angular team on their adoption of semantic versioning and handling of rc. and beta releases. Looks like they are going for a major release every roughly 9 months: http://angularjs.blogspot.com/2016/10/versioning-and-releasing-angular…

Google tends to release code and promote it without really using it much internally first. According to Brad Green, the Engineering Director over Angular, Google AdWords, Google Fiber, and some internal tools are all built with NG2. AdWords is kind of big deal to Google. Edit: source for AdWords reference, http://angularjs.blogspot.com/2015/11/how-google-uses-angular-2-with-d…

There's more info on future plans here: https://angularjs.blogspot.com.au/2016/09/angular2-final.html Specifically: > Bug fixes and non-breaking features for APIs marked as stable > More guides and live examples specific to your use cases > More work on animations > Angular Material 2 > Moving WebWorkers out of experimental > More features and more languages for Angular Universal > Even more speed and payload size improvements And immediately: > Semantic Versioning

Announcement URL http://angularjs.blogspot.ch/2016/09/angular2-final.html

From http://angularjs.blogspot.com/2016/07/a-dedicated-team-for-angulardart… "If you're a TypeScript or JavaScript developer, you'll also benefit from cleaner JavaScript APIs and performance gains as we simplify the TypeScript codebase to remove the need for compilation to Dart." Maybe this split was prompted by the imminent release of Typescript 2.0?

ng2 will work with native script: http://angularjs.blogspot.de/2015/12/building-mobile-apps-with-angular…

Google has been using Angular 1.x for DoubleClick since 2012 (http://angularjs.blogspot.com/2012/06/doubleclick-super-powered-by-ang… I think it's fair to say that it's one of their most important products.

They mentioned Adwords here, too. http://angularjs.blogspot.com/2015/11/highlights-from-angularconnect-2… I'd argue Adwords is one of the most important Google products.

Try using this url instead: http://angularjs.blogspot.com/ncr

The way I chose in the past. Use a jobsite (in my case www.cwjobs.co.uk). Type in framework. Count number of jobs. If one is significantly bigger in the job market, this gives me more flexibility and job security going forward. This has resulted in me going with AngularJS as there are 7-10 times the number of jobs advertised vs other frameworks. My current role also uses typescript and was using it before the Ang 2 announcement. I do watch where the various technologies are going within the whole stack. I also find articles like this interesting as they show movements in the technology stack that I should be aware of http://angularjs.blogspot.co.uk/2015/09/angular-2-survey-results.html I am currently using grunt, but feel I need to get into gulp.

You can upgrade bits and pieces as you learn it: http://angularjs.blogspot.de/2015/08/angular-1-and-angular-2-coexisten… It will end up being no different than any other tech learning curve without breaking your application.

The Angular team has said a few times that they're committed to supporting 1.x for a long time[1] since they use 1.x a ton. Also the design for 2.0 hasn't been completed yet, so it'd be a bit premature to cover it in a codeacademy course [1]http://angularjs.blogspot.com/2014/10/ng-europe-angular-13-and-beyond.…