4 ms·
The intro video is interesting, but the suggestion that apps in Angular are going to be "much more like HTML" seems to me to be belied by the fact that the seco
by indubitably 14y ago
The intro video is interesting, but the suggestion that apps in Angular are going to be "much more like HTML" seems to me to be belied by the fact that the second example has a more or less Backbone-like Model definition.
I can appreciate the desire to have declarative relationships within markup, but if there's going to be Javascript running anyway, what does it gain?
Plus, <html ng-app> is an abomination…
- gregwebs 14y agoYeah, the point of Angular is not to "program in html", just to have declarative html for dealing with the DOM and otherwise program in JS. I totally agree for server-side templates that there are limited benefits (designer friendly perhaps) to a template as valid HTML. However, when you want to make your HTML interactive (2-way data binding) in an unobtrusive way, you are forced to understand html. A good example I went over is how would you bind data to a checkbox automatically? I think you are advocating the Ember.js approach, which uses a function call to represent a checkbox, but a plain tag is actually much easier to understand: http://tunein.yap.tv/javascript/2012/06/11/javascript-frameworks-and-data-binding/ http://tunein.yap.tv/javascript/2012/06/11/javascript-framew...
- patrickaljord 14y ago> Plus, <html ng-app> is an abomination… You can use data-ng-app too which is valid html5.