News for hackers. Stuff that matters.
Re:React vs. Ember – EmberNYC slides by mrcwinn on Tuesday September 02, 2014 @12:47PM (#8258668)
I'm a big fan of React. I soured on Ember but, to be fair, haven't looked at it in quite a while. Curious, though, is the statement in the slide deck that Ember "dominates" big apps true or verifiable? Perhaps if you exclude toolkits/libraries like Backbone, and compare only to Angular, I could buy it.
Re:React vs. Ember – EmberNYC slides by sehr on Tuesday September 02, 2014 @01:34PM (#8258946)
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.

Re:React vs. Ember – EmberNYC slides by belandrew on Tuesday September 02, 2014 @02:27PM (#8259258)
Ember 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.

Re:React vs. Ember – EmberNYC slides by tomdale on Tuesday September 02, 2014 @07:17PM (#8260726)
Those are big companies but not necessarily big apps.
Re:React vs. Ember – EmberNYC slides by xiaoma on Wednesday September 03, 2014 @03:24PM (#8264786)
Which major Google site is built in Angular?
Re:React vs. Ember – EmberNYC slides by mrcwinn on Tuesday September 02, 2014 @02:11PM (#8259159)
Interesting. 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.

Re:React vs. Ember – EmberNYC slides by tomdale on Tuesday September 02, 2014 @02:25PM (#8259241)
Ember 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 or http://twitch.tv.)

Re:React vs. Ember – EmberNYC slides by Retozi on Tuesday September 02, 2014 @02:24PM (#8259234)
I 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).

Re:React vs. Ember – EmberNYC slides by iamstef on Tuesday September 02, 2014 @02:26PM (#8259251)
these are happy-path guidelines and as such, quite easy to diverge from when needed.
Re:React vs. Ember – EmberNYC slides by spicyj on Tuesday September 02, 2014 @01:45PM (#8259023)
> * Khan Academy (also uses loads of React)

(We're writing almost no new Backbone code these days.)

Re:React vs. Ember – EmberNYC slides by sehr on Tuesday September 02, 2014 @01:52PM (#8259058)
Nice! Any plans for working flux into there?
Re:React vs. Ember – EmberNYC slides by spicyj on Tuesday September 02, 2014 @01:58PM (#8259088)
Yup, we've just started recently. Too soon to give any value judgements on it but this article https://news.ycombinator.com/item?id=8248536 made a lot of sense to me and I'm cautiously optimistic about Flux overall.
Re:React vs. Ember – EmberNYC slides by cliftonk on Tuesday September 02, 2014 @04:15PM (#8259875)
For 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

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.

Re:React vs. Ember – EmberNYC slides by KurtMueller on Tuesday September 02, 2014 @03:49PM (#8259718)
Got any open source projects that use flux-react that we could take a look at?
Re:React vs. Ember – EmberNYC slides by spicyj on Tuesday September 02, 2014 @03:51PM (#8259731)
None yet, sorry.
Re:React vs. Ember – EmberNYC slides by codereflection on Tuesday September 02, 2014 @02:25PM (#8259245)
Can 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.
Re:React vs. Ember – EmberNYC slides by sehr on Tuesday September 02, 2014 @03:29PM (#8259590)
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.

Re:React vs. Ember – EmberNYC slides by cavneb on Wednesday September 03, 2014 @11:08AM (#8263340)
Regarding 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.
Re:React vs. Ember – EmberNYC slides by lelelele on Wednesday September 03, 2014 @12:41PM (#8263880)
dsa