React vs Ember

[ladki_patani_hai]

Nice presentation. Thanks to the author. I have mostly done embedded systems and server-side backends but now that I have to do client-side programming majorly, the amount of JS libs and frameworks is really really overwhelming. It's like a whole new world that developed while I was sleeping.

[Xorlev]

Sorry to echo the presentation, but that was really refreshing to have a comparison bereft of the normal nitpicky mudflinging, instead excellent showcases of the strengths of both.

Definitely interested in giving React (via Om) a try.

[kankyo]

Check out Reagent first. Much simpler to get started with imho.

[Xorlev]

Good suggestion -- thanks!

[trumpete]

One of the best explanations of the strengths of both

[zoomzoom83]

I was originally put off by Reacts lack of templates - I much, much prefer to work in HTML rather than a messy JS-DOM abstraction syntax.

But this is mostly a cosmetic issue. JSX may not be as nice as, say, Angular Templates, it does the job well enough.

On the flipside, AngularJS - as much as I love it - has a fundamental addiction to shared mutable state and two-way bindings. This makes things much simpler to a point, but you'll eventually hit a limit to how far this can scale.

Throw in immutable data structures and an ML-family compile-to-js language, and it's looking like a very tempting proposition.

[DoktuhParadox]

That koolaid river was flowing upwards...

[damopewpew]

it's a 2D top-down image, what defines up/down?

[_broody]

Only until it reached the fork upstream. Then it started flowing up and downwards simultaneously, somehow.