ANGULAR, DART and POLYMER : The Holy Trinity of the Future Web? Dart is a better scripting language for the web of the future. It takes the best of javascript, Ruby, Java and C#, it integrates all those functions that once required dozen of libraries (no more need of JQuery, NodeJs, Modernizr.js, etc.), and features a native implementation of the most advanced web technologies around (Polymer.Dart, Angular.Dart, etc.). It is both a server side and client side language making easy to communicate and interoperate between the two, and it also features the coolest core async primitives, Future and Stream, allowing low latency and fast response server design patterns like the React pattern. Dart language is also an open source ECMA standard. But most importantly of all, Dart, being not interpreted but compiled, is 2 to 4 times faster than javascript on the browsers supporting it, and it automatically compiles to javascript on those old browsers that does not support it yet. The moment Google will switch its web code from Javascript to Dart, people will find gsearch, gmail, gdrive, gdocs, gmaps, etc. web sites up to 4 times faster on Dart supporting browsers like Chrome. Then all other browsers will likely start to follow and add native support for offering comparable performances. Hopefully javascript will become a thing of the past.
Yet there are two caveats for BIG PROJECTS at the moment: 1 ) For big projects Polymer is going to rule the web pretty soon. It's disruptive. The polymerization of the web is already underway. Every web site is going to be made from Polymer Elements sooner or later. (look at this video: https://www.youtube.com/watch?v=djQh8XKRzRg ). And while Polymer.Dart is already integrated in Dart, the Dart Editor still doesn't feature a Polymer visual Designer like the one Polymer javascript already has. Also the Core library of Polymer.Dart is still not ready. I would wait for the first Dart Editor released featuring a port of the Polymer Designer ( currently it's javascript only: https://github.com/Polymer/designer/tree/drag-drop ). 2) Angular.Dart is great for big projects. But while Dart supports it better than anyone else, Angular 1.x is not up to date with the modern web. The most important thing missing is a full Polymerization. Angular 2.0 is going to be the real thing, because it will be a native Polymer Element itself. The Angular Views will become canvases for scaffolding polymer elements. You will be able to make Polymer Elements binding together only then. Currently Angular.Dart is still not polymerized, then starting a project now in it will be an error because soon much of the code would likely need to be rewritten. For a big project I would wait for Angular.Dart 2.0. What do you think? Il giorno mercoledì 12 marzo 2014 13:58:48 UTC+1, Jeremy Bell ha scritto: > > From what I've gathered, development of 2.0 appears to be well on its way, > and is starting with some of the components which have been separated out > to (hopefully) allow their use outside of angular (perhaps for code sharing > with the polymer team et. al?). There appear to be at least three > components with public repositories that have appeared in the last few of > months: > > Angular Templating - Added late February, this seems to be the templating > engine, written in ES6 (using a back-compiler to ES5). I'm not sure if this > follows the traditional angular templating model or more closely matches > the MDV spec: > https://github.com/angular/templating > > di.js - Added to github mid-December of last year, this seems to be the > Angular DI framework separated into its own independent framework. Votja > spoke about it at ng-conf (https://www.youtube.com/watch?v=_OGGsf1ZXMs): > https://github.com/angular/di.js > > watchtower - Added to github late February, this is the AngularJS 2.0 > change detection module. It appears to be more or less a port of the dart > change detection code: > https://github.com/angular/watchtower.js > > Angular 2.0 is also going to be based off of the Web Components pollyfill > contained in the Polymer project (platform.js) without the higher level > code on top of that. It's unclear what kind of code sharing/collaboration > those two teams will do, but so far the word has been that the two teams > will work together on platform.js at a minimum. Angular 2.0 also appears to > be heavily influenced by AngularDart, which already supports Web Components > through Dart's implementation. > > Regards, > -Jeremy > > On Tuesday, March 11, 2014 2:52:28 AM UTC-4, Sander Elias wrote: >> >> Hi Adam, >> >> Angular 2.0 is in the planning stage, It's discussed by the core team, >> parts are being build as we speak. There is (as far a I know of) not (yet) >> a central repository. There are references on how to get involved all over >> the place, The best way is through the github projects, fork, comment and >> send pull requests will do it. I keep a close watch on anything that's >> being released, and I read trough anything I can lay my hands on. >> the G+ AngularJS group is a good place to start. >> >> Regards >> Sander >> > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
