5 ms·

Ha ha, nice way to scare people off angular and justify their decision ;) Transclusions are an interesting feature to cherry pick because a) they're a necessary

by nkerkin 14y ago

Ha ha, nice way to scare people off angular and justify their decision ;) Transclusions are an interesting feature to cherry pick because a) they're a necessary complexity to enable reusable components (one of angular's greatest strengths), and b) they highlight the steep learning curve required to truly master angular. I agree that the docs can be a bit vague occasionally, but I think that's only due to the sheer depth of features and flexibility that angular provides. I was a skeptic for a long time (was championing knockout.js), but having used it in both personal and professional projects, I'm a convert. Angular is a thoroughly well designed library, that gets the hell out of your way.

codygman 14y ago
I wasn't trying to scare people off of angular, as it's what I am currently trying to use. I find it to be a very good framework, but also plan on checking out ember.js to see if it provides more for me overall or not.
- nkerkin 14y ago
  Yeah, sorry, was referring to the discourse article, not meaning to implicate you.
codygman 14y ago
Can you share what converted you from knockout to to angular? What were the big reasons? What was the tipping point?
- nkerkin 14y ago
  A few things really: 1) a good friend recommended angular to me, in pre-1.0 days, the site was horrid, and I just couldn't grok angular. The framework, site and docs have improved drastically over the last year. 2) I was initially against angular's declarative markup style, thou shalt not mix html and code, etc. But after spending a bit of time getting unobtrusive bindings to work with KO [1], and then looking at the angular equivalent functionality [2], I was sold. 3) Having to massage "business-logic" code into ko.observable* (or DS.*) is quite arduous, angular does 2-way binding on plain old JS objects. 4) Angular templates are logic-less and it strongly encourages you to put your logic into your controllers, where it can be easily tested. In the end KO is a template-binding library, whereas angular and ember are full stack. [1] http://gratdevel.blogspot.com.au/2012/02/exploring-todomvc-and-knockoutjs-with.html http://gratdevel.blogspot.com.au/2012/02/exploring-todomvc-a... [2] http://angularjs.org/#add-some-control http://angularjs.org/#add-some-control
gkatsanos 14y ago
if you think Angular docs are vague, go check Ember. (what docs?)
- cgcardona 14y ago
  _These_ docs: Ember.JS Guides: http://emberjs.com/guides/ http://emberjs.com/guides/ Ember.js API Docs: http://emberjs.com/api/ http://emberjs.com/api/ To be fair there have been a bunch of API changes but as of yesterday Version: v1.0.0-rc.1 is released. This means that the API for Ember.js should now be much more stable going forward. The next step is to get Ember-Data to where it's stable and then merge it into Ember.js proper.

by nkerkin 14y ago

codygman 14y ago

I wasn't trying to scare people off of angular, as it's what I am currently trying to use. I find it to be a very good framework, but also plan on checking out ember.js to see if it provides more for me overall or not.

nkerkin 14y ago
Yeah, sorry, was referring to the discourse article, not meaning to implicate you.

codygman 14y ago

Can you share what converted you from knockout to to angular? What were the big reasons? What was the tipping point?

nkerkin 14y ago
A few things really: 1) a good friend recommended angular to me, in pre-1.0 days, the site was horrid, and I just couldn't grok angular. The framework, site and docs have improved drastically over the last year. 2) I was initially against angular's declarative markup style, thou shalt not mix html and code, etc. But after spending a bit of time getting unobtrusive bindings to work with KO [1], and then looking at the angular equivalent functionality [2], I was sold. 3) Having to massage "business-logic" code into ko.observable* (or DS.*) is quite arduous, angular does 2-way binding on plain old JS objects. 4) Angular templates are logic-less and it strongly encourages you to put your logic into your controllers, where it can be easily tested. In the end KO is a template-binding library, whereas angular and ember are full stack. [1] http://gratdevel.blogspot.com.au/2012/02/exploring-todomvc-and-knockoutjs-with.html http://gratdevel.blogspot.com.au/2012/02/exploring-todomvc-a... [2] http://angularjs.org/#add-some-control http://angularjs.org/#add-some-control

gkatsanos 14y ago

if you think Angular docs are vague, go check Ember. (what docs?)

cgcardona 14y ago
_These_ docs: Ember.JS Guides: http://emberjs.com/guides/ http://emberjs.com/guides/ Ember.js API Docs: http://emberjs.com/api/ http://emberjs.com/api/ To be fair there have been a bunch of API changes but as of yesterday Version: v1.0.0-rc.1 is released. This means that the API for Ember.js should now be much more stable going forward. The next step is to get Ember-Data to where it's stable and then merge it into Ember.js proper.