3 ms·
Having just dug into Angular while wondering if I really wanted to be working with Ember, this was a great comparison. It's obvious to me now I have to look at
by sailfast 13y ago
Having just dug into Angular while wondering if I really wanted to be working with Ember, this was a great comparison. It's obvious to me now I have to look at both frameworks. While done by an Ember.js creator I found the presentation also provided me with a much deeper knowledge of Angular at the same time - well done.
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.
- machty 13y agoI 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
- bib971 13y agoWhat do you mean "Angular encourages you to build the framework"? What kind of framework?
- trek 13y agoThe framework appropriate to the kind application you want to build
- steveklabnik 13y agoThe answer is in the deck. https://docs.google.com/a/steveklabnik.com/presentation/d/1e0z1pT9JuEh8G5DOtib6XFDHK0GUFtrZrU3IfxJynaA/preview#slide=id.g177e4bd2b_0192 https://docs.google.com/a/steveklabnik.com/presentation/d/1e...
- veemjeem 13y agoit is also on slide 53
- thatthatis 13y agoMy 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.