Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#1

Post by vlad » Thu, May 30, 2013, 3:47 AM UTC

Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS
medium.com

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#2

Post by jval » Thu, May 30, 2013, 4:20 AM UTC

Neat, although I'm more interested in when you plan on having this book out... Angular is incredibly powerful but it really could use with some more resources for those who are picking it up.

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#3

Post by twiceaday » Thu, May 30, 2013, 4:23 AM UTC

This blog does some interesting stuff if you mouse-wheel-click and drag past an edge.

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#4

Post by MatthewPhillips » Thu, May 30, 2013, 4:26 AM UTC

Seeing the word "controller" in markup makes me want to gag myself.

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#5

Post by jonursenbach » Thu, May 30, 2013, 4:27 AM UTC

MatthewPhillips wrote: post #4

Seeing the word "controller" in markup makes me want to gag myself.

Why?

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#6

Post by MatthewPhillips » Thu, May 30, 2013, 4:29 AM UTC

jonursenbach wrote: post #5

MatthewPhillips wrote: post #4

Seeing the word "controller" in markup makes me want to gag myself.

Why?

Separation of concerns

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#7

Post by eric_bullington » Thu, May 30, 2013, 4:39 AM UTC

MatthewPhillips wrote: post #6

jonursenbach wrote: post #5

Earlier quoted context omitted.

Why?

Separation of concerns

The controller is in fact separated. The "ngController" you see referenced in the markup is the link between the view and the separate controller. Any MVC framework you could hold up as an example of proper "separation of concerns" will necessarily have the same link, even if it's implicit. Sometimes it's defined in the controller, sometimes the link is defined in the view, and sometimes you don't see it defined, but it's still there. (of course, we all know explicit is better than implicit)

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#8

Post by MatthewPhillips » Thu, May 30, 2013, 4:48 AM UTC

eric_bullington wrote: post #7

MatthewPhillips wrote: post #6

Earlier quoted context omitted.

Separation of concerns

The controller is in fact separated. The "ngController" you see referenced in the markup is the link between the view and the separate controller. Any MVC framework you could hold up as an example of proper "separation of concerns" will necessarily have the same link, even if it's implicit. Sometimes it's defined in the controller, sometimes the link is defined in the view, and sometimes you don't see it defined, but…

Right, but doing it this way means both the view and the controller know too much. Why should a view know about how it is going to be used? Also, I'm guessing if you give this to a designer his/her eyes are going to glaze over.

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#9

Post by mugenx86 » Thu, May 30, 2013, 4:52 AM UTC

I'm struggling to find an advantage that React has over AngularJS.

+1 for AngularJS

Re: Facebook’s New React JavaScript Library Tutorial Rewritten in AngularJS

#10

Post by mugenx86 » Thu, May 30, 2013, 4:56 AM UTC

MatthewPhillips wrote: post #4

Seeing the word "controller" in markup makes me want to gag myself.

The controller directive is necessary to determine the scope of the variables/functions embedded in the view.

But I do agree on the point that designers would certainly gag when seeing this... A developer would need to go though the deign and insert all the hooks. This step is unavoidable with any web application framework.

That being said, I think a designer would puke if they were required to write React components.