Re:AngularJS from an Ember.js perspective
by machty on Thursday November 21, 2013 @03:38PM
(#6777310)
I just added this to the slides (ran out of time to prepare/say all the things I wanted to), related to Google popularity:
- A toolset’s mindshare is predictably going to be greater than that of a framework
- Angular interest (per Google) dwarfs Ember; jQuery interest dwarfs Angular, etc
- Angular encourages you to build the framework; Ember is the framework
Re:AngularJS from an Ember.js perspective
by bib971 on Thursday November 21, 2013 @04:04PM
(#6777475)
What do you mean "Angular encourages you to build the framework"? What kind of framework?
Re:AngularJS from an Ember.js perspective
by steveklabnik on Thursday November 21, 2013 @04:13PM
(#6777534)
The answer is in the deck.
https://docs.google.com/a/steveklabnik.com/presentation/d/1e...
Re:AngularJS from an Ember.js perspective
by veemjeem on Thursday November 21, 2013 @07:47PM
(#6778582)
it is also on slide 53
The framework appropriate to the kind application you want to build
Re:AngularJS from an Ember.js perspective
by thatthatis on Friday November 22, 2013 @11:19AM
(#6781668)
My usual trick for getting around this is in rails vs django is to add tutorial to the search, so "emberjs tutorial" and "angularjs tutorial." Unfortunately it looks like we're still too early to have enough data using those terms, which tells me that the google search data should be taken with an enormous grain of salt.
As for the Google popularity, one could snidely remark that Angular's documentation and taxonomy requires significant amounts of searching to solve the problems you are after. While the community is active, it's quite difficult to find examples of the right solution or effective documentation for newbies at times.