5 ms·
Ember definitely smashes Angular in terms of 'big apps', it seems it's somewhat behind Backbone. Ember: * Vine * Twitch * Square * Heroku (dashboard) * NB
by sehr 12y ago
Ember definitely smashes Angular in terms of 'big apps', it seems it's somewhat behind Backbone.
Ember:
* Vine
* Twitch
* Square
* Heroku (dashboard)
* NBC News
* Discourse
* Huboard
* Travis CI
Backbone:
* Rdio
* Hulu
* Disqus
* Khan Academy (also uses loads of React)
* Stripe
* AirBnB
* Pandora
* Trello
etc etc..
Backbone has been around a lot longer, but Ember's apps seems to be built more recently.
- spicyj 12y ago> * Khan Academy (also uses loads of React) (We're writing almost no new Backbone code these days.)
- sehr 12y agoNice! Any plans for working flux into there?
- spicyj 12y agoYup, we've just started recently. Too soon to give any value judgements on it but this article https://news.ycombinator.com/item?id=8248536 https://news.ycombinator.com/item?id=8248536 made a lot of sense to me and I'm cautiously optimistic about Flux overall.
- KurtMueller 12y agoGot any open source projects that use flux-react that we could take a look at?
- spicyj 12y agoNone yet, sorry.
- cliftonk 12y agoFor pages with a great deal of local/global state, we've taken a page from David Nolen's Om library and have a cursors library written for react using react's immutability helpers. See the example/repo @ https://github.com/caseywebdev/cursors https://github.com/caseywebdev/cursors IMO, pairing global page pub/sub with heavy local modification doesn't seem like a good pattern for effective state management. It seems less problematic at scale than two-way databinding but problematic nonetheless.
- mrcwinn 12y agoInteresting. Thanks for the list. My biggest issue with Ember, other than the management of release schedule and API early on, is the concept of tying routes to models explicitly. It seems to assume that given a route context, you'll be dealing with a particular model - and only one particular model. If you want to have an additional data context, you need to establish route and then tie the routes together within one template. This seems to confuse the relationship between a URL and the data displayed on the page. I've really enjoyed React+Backbone, on the other hand. Very small footprint and gives me flexibility to design and build an application. After spending years with Rails, I've come around to "convention over configuration" is a nice thought, but breaks down at certain sizes. And it seems to break down much more quickly on the client side. To me, personally, well-written Backbone+Underscore+React runs circles around the newer JavaScript frameworks. It's not to say the debate is over and settled - I just haven't found the complexity and size of frameworks like Ember to pay back more than they cost.
- deleted 12y ago[deleted]
- Retozi 12y agoI feel like these somewhat restricting patterns can increase your productivity massively. If your app fits the restriction. If not, it will slow you down. There is usually not enough emphasis on the nature of the app in these X vs Y framework discussions. I can really see why you would choose Ember say for Discourse and why (once you got it) it is very productive. But for other apps you might constantly fight the Framework. Optimal patterns really depend on what you want/need to do. (Thats why TodoMVC doesn't help much).
- tomdale 12y agoEmber has now got one of the best (IMO) release cycles in the business. We borrow heavily from Chrome, and have a very polished release infrastructure, with release, beta and canary channels you can subscribe to. Additionally, we have a strict commitment to SemVer and most Ember apps are on the latest release. As for the complaint about tying models to routes: Ember does want you to have a model per route, but the model can be any data structure you want: an array, a hash with multiple models, or a single model. I'm not sure exactly what issue you hit, but most apps of any complexity have multiple models on the page, and of course that's something we support out of the box. (You can see this if you open any production Ember app in the Ember Inspector browser extension, such as http://vine.co http://vine.co or http://twitch.tv. http://twitch.tv.)
- codereflection 12y agoCan you provide proof that Angular is not being used to build similar big apps? The quick research I've done shows the opposite, and that Angular adoption is quite a bit higher than Ember.
- sehr 12y agohttps://builtwith.angularjs.org/ https://builtwith.angularjs.org/ Mostly small projects and stuff. Angular definitely has a larger community, but from what I can gather on the internet Ember is used much more often as the entire basis for large applications.
- cavneb 12y agoRegarding https://builtwith.angularjs.org/ https://builtwith.angularjs.org/, It kills me how a page so important to the marketing of Angular is so poorly put together. The pagination wraps over the footer and if I go to another page and refresh, it starts over. I'm not an Angular hater by any means, but I would think that it might be important to at least have a clean experience when trying to market the framework.
- belandrew 12y agoEmber isn't smashing anything. Besides the obvious Google, Angular is used by Udacity, Nike, Virgin America, HBO's mobile app, MSNBC, Salesforce, Amazon AWS, Sony's PS3 Youtube app, and General Motor's in-car interface. Sounds like plenty of big apps to me. Edit: Added GM.