3 ms·

Perhaps data-ng-* should then be the default, as another commenter has suggested. The Web Component spec[1] examples always have the template in plain HTML, wr

Perhaps data-ng-* should then be the default, as another commenter has suggested. The Web Component spec[1] examples always have the template in plain HTML, wrapped in a <template> and separate from any JavaScript. Searching the AngularJS site, there are zero references to "Web Components". Web Components are so new that the spec still has Norse mythology references, so a reference from Angular to the spec would be a big help. More importantly, while Angular has been duplicating the functionality of Underscore and jQuery, the rest of the JS world is extending itself with CommonJS modules according to spec. Half of the builtwith.angularjs.org examples include jQuery anyway. Angular's attempt to be a complete "end-to-end solution" may easily make it a jack-of-all-trades, master of none. This also seems at odds with its focus on being a component. Lastly, I am not the first person to raise these concerns.[2] [1] http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/i... [2] https://groups.google.com/group/angular/tree/browse_frm/month/2011-10/8b97d0945601b07b?rnum=11&lnk=nl https://groups.google.com/group/angular/tree/browse_frm/mont...

patrickaljord 14y ago
https://plus.google.com/104744871076396904202/posts/1ThZhwVSnQF https://plus.google.com/104744871076396904202/posts/1ThZhwVS... From one of AngularJS author: > AngularJS is our testbed to see what works and what doesn't. We are taking the best ideas from angular and use them to shape the (Web Components) specs (and the other way around too!). As the first step, we are hoping to start to replace some pieces of angular when native apis are available. we'll see how far we'll get with this approach. What is important is that Angular can help you start thinking in the way that will be required for using these native apis and believe me that is a huge plus already. So not only do they care about Web Components, they are using AngularJS to shape the specs and vice versa. Hard to be more standard than given that the specs are still unstable. About being able to re-use the code on server side, I don't care about that, I write my apps in ruby anyway and this is out of scope of a JS MVC anyway. The only people that might care about that are Node users, and most people don't use Node or other js server side. So that's a non issue.

patrickaljord 14y ago

https://plus.google.com/104744871076396904202/posts/1ThZhwVSnQF https://plus.google.com/104744871076396904202/posts/1ThZhwVS... From one of AngularJS author: > AngularJS is our testbed to see what works and what doesn't. We are taking the best ideas from angular and use them to shape the (Web Components) specs (and the other way around too!). As the first step, we are hoping to start to replace some pieces of angular when native apis are available. we'll see how far we'll get with this approach. What is important is that Angular can help you start thinking in the way that will be required for using these native apis and believe me that is a huge plus already. So not only do they care about Web Components, they are using AngularJS to shape the specs and vice versa. Hard to be more standard than given that the specs are still unstable. About being able to re-use the code on server side, I don't care about that, I write my apps in ruby anyway and this is out of scope of a JS MVC anyway. The only people that might care about that are Node users, and most people don't use Node or other js server side. So that's a non issue.