27 ms·

Getting started with Ember is a lot harder than your comment admits. I tried Ember recently and there was still a lot of stuff that was broken including the da

Getting started with Ember is a lot harder than your comment admits. I tried Ember recently and there was still a lot of stuff that was broken including the data model. That would make building a non-trivial app hard.

davidw 14y ago
What I'm investigating Backbone/Ember/whatever for is a semi-embedded device that will ship with a web interface, so some semblance of stability is a major plus.
- throwa 14y ago
  As we speak it is used in production by many companies. Click this link to see them all: https://github.com/emberjs/ember.js/wiki/Production-Deployments-Page https://github.com/emberjs/ember.js/wiki/Production-Deployme... Shopitome is a very fresh deployment using emberjs based on this tweet sent today: http://twitter.com/inkredabull/status/268017623428657153 http://twitter.com/inkredabull/status/268017623428657153 http://www.shopittome.com/threads/signup http://www.shopittome.com/threads/signup A few non trivial companies using emberjs in production are: www.zendesk.com http://www.squareup.com/ http://www.squareup.com/ http://livingsocial.com/ http://livingsocial.com/ http://www.groupon.com http://www.groupon.com http://www.desk.com/ http://www.desk.com/ http://basho.com/ http://basho.com/ http://travis-ci.org/ http://travis-ci.org/ http://www.gooddata.com/ http://www.gooddata.com/
  - davidw 14y ago
    Web production != shipping on devices production. You can very easily ship updates to the former whereas the latter is tricky. It means we need to be careful with everything we choose.
throwa 14y ago
@atomical, the link to trek's article above puts it more succintly: Ember applications start out with a complexity rating of 4/10 but never get much higher than 6/10, regardless of how sophisticated your application becomes. Backbone starts out at 1/10 but complexity grows linearly. This is a natural side effect of the types of applications the two frameworks were specifically created for.

davidw 14y ago

What I'm investigating Backbone/Ember/whatever for is a semi-embedded device that will ship with a web interface, so some semblance of stability is a major plus.

throwa 14y ago
As we speak it is used in production by many companies. Click this link to see them all: https://github.com/emberjs/ember.js/wiki/Production-Deployments-Page https://github.com/emberjs/ember.js/wiki/Production-Deployme... Shopitome is a very fresh deployment using emberjs based on this tweet sent today: http://twitter.com/inkredabull/status/268017623428657153 http://twitter.com/inkredabull/status/268017623428657153 http://www.shopittome.com/threads/signup http://www.shopittome.com/threads/signup A few non trivial companies using emberjs in production are: www.zendesk.com http://www.squareup.com/ http://www.squareup.com/ http://livingsocial.com/ http://livingsocial.com/ http://www.groupon.com http://www.groupon.com http://www.desk.com/ http://www.desk.com/ http://basho.com/ http://basho.com/ http://travis-ci.org/ http://travis-ci.org/ http://www.gooddata.com/ http://www.gooddata.com/
- davidw 14y ago
  Web production != shipping on devices production. You can very easily ship updates to the former whereas the latter is tricky. It means we need to be careful with everything we choose.

throwa 14y ago

@atomical, the link to trek's article above puts it more succintly: Ember applications start out with a complexity rating of 4/10 but never get much higher than 6/10, regardless of how sophisticated your application becomes. Backbone starts out at 1/10 but complexity grows linearly. This is a natural side effect of the types of applications the two frameworks were specifically created for.