4 ms·
Wow, the Angular version is so small. Very impressed with the clean, readable, and terse code. Thanks guys.
by wheaties 14y ago
Wow, the Angular version is so small. Very impressed with the clean, readable, and terse code. Thanks guys.
- wiradikusuma 14y agobut not small enough. i just recently 'convert' from backbone to angular, so i'm bias. but i dont understand why on earth the js needs to be seperated instead of everything in 1 js file. only then people can say, "is this all? wow!" and i cant help but wonder why the actions need to be in 'form' element. angular can do ng-click just fine.
- nkerkin 14y agoCheck out http://jsfiddle.net/api/post/library/pure/ http://jsfiddle.net/api/post/library/pure/, it uses a single file for the entire angular app. From my experience, spreading services, controllers, etc over multiple files is just for convenience.
- nkerkin 14y agoBah, ignore that. Try out the JSFiddle linked for the "Wire up a Backend" example on http://angularjs.org/ http://angularjs.org/
- delambo 14y agoIt's not so small when you add up all of the obtrusive javascript/framework code that is littered throughout the html: <li ng-repeat="todo in todos | filter:statusFilter" ng-class="{completed: todo.completed, editing: todo == editedTodo}"> ... which some may consider a bigger problem than size.
- johne20 14y agoWe recently had to make a choice between frameworks and my colleague and I came from a jquery/rails background, virtually no practical experience with js frameworks. We started with backbone.js, but I was immediately frustrated. We then switched to angular.js after going through the tutorial ~2hrs. Four months and a lot of learning later, I am very happy with our choice. If I ever get some spare time I want to write some posts on angular from a rails perspective. I found the rails nomenclature I was used to didn't directly translate to angular. One other reason we chose angular, it is backed by Google. The meetups I have attended in Seattle keep growing steadily and the mailing list is great.
- drumdance 14y agoPLEASE write this up. :) I'm in a similar boat. I have a fair amount of legacy code I would need to port over, so I'd especially like to know what the transition was like (if that applies to your situation). Edit: also, vis a vis Rails I'm curious whether and how it's possible to handle validations on the client side without having to duplicate everything in the Rails model.
- delambo 14y ago> One other reason we chose angular, it is backed by Google. I like Google for many things - there is no doubt they have some solid developers and have released great products - but they have a poor track record with frontend framework adoption. For example: - GWT (not a lot of adoption and waning) - Closure Tools (except for the great Google products that are built with this library and closure compiler it hasn't had a lot of adoption) - Dart (verdict is still out on this one but it doesn't look good)
- edwinyzh 14y agoYes! AngularJS's concept is similar to RAD frameworks such as VCL (in Delphi) and the UI frameworks in .net frameworks on Windows.