Note that the new strategy for the 2.0 version Angular will make this new relatively web application framework definitely the number one, as the current 1.x version of AngularJS is already attractzing more interest than the previous stars such as Ruby on Rails and Django (contemporary competitors like Backbone.js and Ember.js are no match either):
According to the current (March 5) status of ES 6:
… Development of the ECME-262 6h Edition, The 2015 ECMAScript Language Specification is complete. All that remains to find and fix and remaining editorial or technical bugs in the document. …
March 4, 2015 Rev 35 Release Candidate 2
as well as to the TC39 – ECMAScript – Ecma International:
… A sixth edition of the standard is currently under development with a target date of June 2015 for completion. …
This week my friend Dan Wahlin and I presented at ng-conf as it will get posted soon. There was even some fantastic news that came out about TypeScript and Angular at the show – instead of proceeding with AtScript, the Angular team worked with the TypeScript team to extend the language and make it even better!
- Catch coding issues faster – When you have static types, the compiler and IDEs can help you more, showing errors and possible issues before you have to run your app to find those errors.
ng-conf 2015, March 6, 2015:
TypeScript and Angular 2.0 ¦ Jonathan Turner [Program Manager on TypeScript, Microsoft, he has been a part of the TypeScript team since its first public release in October 2012]
One of the best aids to good craftsmen is the tools they use. In this session, we’ll be looking at upcoming features of TypeScript and related tools and how these features help you get the most out of your Angular 2.0 development.
March 5, 2015 by Jonathan Turner: Angular 2: Built on TypeScript
We’re excited to unveil the result of a months-long partnership with the Angular team.
This partnership has been very productive and rewarding experience for us, and as part of this collaboration, we’re happy to announce that Angular 2 will now be built with TypeScript. We’re looking forward to seeing what people will be able to do with these new tools and continuing to work with the Angular team to improve the experience for Angular developers.
The first fruits of this collaboration will be in the upcoming TypeScript 1.5 release.
We have worked with the Angular team to design a set of new features that will help you develop cleaner code when working with dynamic libraries like Angular 2, including a new way to annotate class declarations with metadata. Library and application developers can use these metadata annotations to cleanly separate code from information about the code, such as configuration information or conditional compilation checks.
We’ve also added a way to retrieve type information at runtime. When enabled, this will enable developers to do a simple type introspection. To verify code correctness with additional runtime checks. It also enables libraries like Angular to use type information to set up dependency injection based on the types themselves.
TodoMVC for Angular 2 in TypeScript
At ng-conf, we are previewing this work by showing a TodoMVC example, based on David East’s Angular 2 TodoMVC. You can try this example out for yourself. If you’re new to TypeScript, you can also learn TypeScript through our interactive playground.
We’re looking forward to releasing a beta of TypeScript 1.5 in the coming weeks, and along with it, growing TypeScript’s tooling support to include more development styles and environments.
/TypeScript, March 5, 2015:
Roadmap by Anders Hejlsberg
- Language service re-write to target new compiler
- Support for protected members in classes
- Support for Tuple Types
- Support for Union Types and Type Guards
- New –noEmitOnError
- New –target ES6
- Support for Let and Const
- Support for Template Strings
- Library typings for ES6
- Support for Const enums
- Export Language Service public API
[“nearly closes the gap with ES6 features”, Beta out in a few weeks]
- Support for Destructuring
- Support for Spread Operator
- Support for ES6 Modules
- Support for for..of
- Support for ES6 Unicode specification
- Support for Symbols
- Support for Computed properties
- Support for tsconfig.json files
- Support for let and const on ES3/ES5
- Support for tagged string templates on ES3/ES5
- Expose a new editor interface through TS Server
- Support for local types and class expressions
- Investigate top-rated feature requests (mixins, abstract classes, etc).
- Improve lib.d.ts modularity
ng-conf 2015, March 5, 2015:
Angular 2, Collaboration between Angular team and TypeScript team, investment in Dart, partnering with Ember (as an example), Simpler-Standards-Performance measured with benchmarks etc.
From Welcome keynote on the 1st day (by Brad Green [engineering director at Google for Google Sales Platform suite of projects as well as the Angular framework] and Igor Minar [lead on the Angular project] to start with, then Jonathan Turner from Microsoft). The full keynote starts with Angular 1 related things.
ng-conf 2015, March 6, 2015:
Demo of Angular 2 with TypeScript running in the browser
(the result of just a couple of months work, with just a few components available and with Alpha code)
From All about Angular 2 keynote on the 2nd day of ng-conf 2015 (by Miško Hevery the creator of Angular framework, and Rado Kirov doing the demo). The full keynote starts with talk about: Angular 2 Syntax (Familiar vs Simple, event binding, ref binding); Web Components (Microsyntax, Simpler – Predictable – Toolable).
Update: March 25, 2015
Dart for the Entire Web by Lars Bak & Kasper Lund, Dart co-founders
Dart developers outside of Google are also very supportive of our new focus. When DGLogik, developers of Internet of Things applications, needed to convert their complex visualization software from Flash to HTML5, they chose Dart because “the Dart team’s focus on the entire web ensures we continue to deliver great experiences for all our users.” Dennis Khvostionov, CTO of DGLogik, continues: “Without Dart’s productivity benefits and tooling, we’d need a team twice our size.”
Many of our developers use Dart for both client and server apps, reducing costs by sharing code. We remain committed to optimizing and improving the Dart VM for developer tools, servers, and mobile apps.
We started the Dart project because we believe that every developer deserves simplicity, productivity, and performance. Our new web strategy makes it easier for developers to build with, and for, the modern web with Dart. With Google Ads’ long-term commitment to Dart, and our new focused strategy for the web, we are excited by our path forward.