3 ms·
We 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 framew
by johne20 14y ago
We 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)