News for hackers. Stuff that matters.
Re:Choosing the Right JavaScript Framework by andrewvc on Thursday August 21, 2014 @11:56AM (#8207962)
What, no React/Flux? How can this be a serious comparison without React?
Re:Choosing the Right JavaScript Framework by megaman821 on Thursday August 21, 2014 @12:51PM (#8208298)
React + what? Is there a standard router/controller and model that get's used with React?

I think they just could have added the line "As an alternative to using underscore templates in Backbone, you can use React instead."

Re:Choosing the Right JavaScript Framework by compedit on Thursday August 21, 2014 @01:57PM (#8208676)
There's no standards, but at this point I'd say Flux + React-router are quickly becoming it. react-router is made in the spirit of Ember's which is pretty well liked.

- Flux Architecture Pattern [0]

- React Router [1]

Note that there isn't really a prescribed model in Angular aside from $scope either.

[0] - http://facebook.github.io/flux/

[1] - https://github.com/rackt/react-router

Re:Choosing the Right JavaScript Framework by megaman821 on Thursday August 21, 2014 @03:29PM (#8209125)
I like react-router that looks quite nice. Flux looks like a description of an idea rather a JavaScript library. Is there a flux store that persists to a REST backend?

A model really isn't part of Angular core since it was split out but something like angular-resource is what I am talking about.

Re:Choosing the Right JavaScript Framework by compedit on Thursday August 21, 2014 @04:07PM (#8209289)
I'd recommend looking at the docs on Flux, it explains it all better than I could.
Re:Choosing the Right JavaScript Framework by andrewvc on Thursday August 21, 2014 @01:56PM (#8208670)
Well, react/flux completely replaces backbone except for the router. The models go away completely, as do the views.
Re:Choosing the Right JavaScript Framework by nacs on Thursday August 21, 2014 @01:34PM (#8208542)
There are a couple React-only routers but a lot of React.js people (including myself) use Backbone for the router/controller.
Re:Choosing the Right JavaScript Framework by andrewvc on Thursday August 21, 2014 @01:55PM (#8208661)
I'm actually using 'director' which works great, much simpler.
Re:Choosing the Right JavaScript Framework by quangv on Thursday August 21, 2014 @12:08PM (#8208051)
Yes, agreed ? I prefer it over Angular/Ember/Backbone
Re:Choosing the Right JavaScript Framework by cnp on Thursday August 21, 2014 @12:16PM (#8208092)
Far superior, far simpler, but it's not exactly a framework :/
Re:Choosing the Right JavaScript Framework by kaonashi on Thursday August 21, 2014 @12:32PM (#8208180)
Which is exactly why you should choose it.
Re:Choosing the Right JavaScript Framework by swah on Thursday August 21, 2014 @12:43PM (#8208252)
How could I do something like http://ichord.github.com/At.js in React?
Re:Choosing the Right JavaScript Framework by kaonashi on Thursday August 21, 2014 @12:48PM (#8208288)
React would handle the DOM; you would have to have some data model that handles the autocomplete list/cursor position and then feeds the results back into the react component.
Re:Choosing the Right JavaScript Framework by cnp on Friday August 22, 2014 @09:02PM (#8214629)
Exactly :)
Re:Choosing the Right JavaScript Framework by capkutay on Thursday August 21, 2014 @12:24PM (#8208136)
Flux might still be in the early adopter phase. Version 0.11 might be nice for side projects, but I'd feel uncomfortable trying to deploy a commercial app using a project that has been available to the public for less than 6 months.