3 ms·

I sorta learn Angularjs, well went through a few tutorials on Angular for a company. Turned out that company is now doing emberjs and I have to learn emberjs.

I sorta learn Angularjs, well went through a few tutorials on Angular for a company. Turned out that company is now doing emberjs and I have to learn emberjs. I have to say EmberData is not production ready. It's modularity is more monolithic compare to Angularjs. There's a lot of moving parts that can break (in term of using emblem, brunch, handlebar, etc...). And the community is much smaller, less books, less people that talks about ember/tutorial etc... Angularjs, it seems much better but the scoping can be a hassle. I feel like angularjs is winning right now in term of hype, community, resources (books, blogs, etc..), and overall I feel like angular got it right and more ready (cause emberdata ain't ready). On the plus side, ember got a cute mascot and angular got nothing... Although this is just my initial reaction and it can change over time. Hopefully Ember will get better but if I have a side project I would chose angularjs over emberjs right now. Unless ember changed for the better. edit: direct injection is pretty awesome in angular btw.

iamstef 13y ago
comparing angular to ember-data seems strange, no?
- digitalzombie 13y ago
  Well my reasoning is because angular have a so called model. It's scope. Angular doesn't need a model, it's a MV whatever. Where as ember is MVC. The framework is MVC and it's M is not complete at all. So judging from an overall framework ember is not complete in that respect where as Angular is. Like come on, 1.0 and hey our M in our MVC framework is incomplete. Um... that's shouldn't even be 1.0. 1.0 to them is the api is going to be stable but not the emberdata, the model. Really?
  - iamstef 13y ago
    o_0)
  - Kerrick 13y ago
    Ember.Object is the M in the Ember.js MVC framework. Ember Data is a library to synchronize a RESTful API with your models, without ever writing a line of networking or AJAX code.
  - bwilliams 13y ago
    Nobody is forcing you to use Ember Data. There's quite a few alternatives out there and you can even use $.ajax. This is a very unfair comparison between a complete stable release of Angular and an alpha of Ember Data that even tells you it's extremely unstable and not production ready.
- Wilya 13y ago
  One of the problem is that the tutorial on the emberjs website makes use of ember-data and doesn't show you anything else. You have to dig a bit further to realize what exactly the distinction is and what you can use instead of ember-data. It doesn't really make it explicit (maybe on purpose) that ember and ember-data are distinct projects.

iamstef 13y ago

comparing angular to ember-data seems strange, no?

digitalzombie 13y ago
Well my reasoning is because angular have a so called model. It's scope. Angular doesn't need a model, it's a MV whatever. Where as ember is MVC. The framework is MVC and it's M is not complete at all. So judging from an overall framework ember is not complete in that respect where as Angular is. Like come on, 1.0 and hey our M in our MVC framework is incomplete. Um... that's shouldn't even be 1.0. 1.0 to them is the api is going to be stable but not the emberdata, the model. Really?
- iamstef 13y ago
  o_0)
- Kerrick 13y ago
  Ember.Object is the M in the Ember.js MVC framework. Ember Data is a library to synchronize a RESTful API with your models, without ever writing a line of networking or AJAX code.
- bwilliams 13y ago
  Nobody is forcing you to use Ember Data. There's quite a few alternatives out there and you can even use $.ajax. This is a very unfair comparison between a complete stable release of Angular and an alpha of Ember Data that even tells you it's extremely unstable and not production ready.
Wilya 13y ago
One of the problem is that the tutorial on the emberjs website makes use of ember-data and doesn't show you anything else. You have to dig a bit further to realize what exactly the distinction is and what you can use instead of ember-data. It doesn't really make it explicit (maybe on purpose) that ember and ember-data are distinct projects.