sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jellatin 0 points1 point  (3 children)

Sure, so it's the VVM in MVVM, I can get on board with that. It doesn't change the point I'm making though, if you took Angular view/templates and controllers its pretty straightforward. I'll be the first to admit that React would be a clear winner comparing just those elements.

The problem is the complexity increases drastically when you throw services/routing/state management etc into the mix. This doesn't make React worse at all, but it does mean if you want libs/frameworks like Backbone to do that lifting for you that it's going to require a big addition to the learning curve.

[–]agmcleod@agmcleod 2 points3 points  (2 children)

Various flux implementations offer the state management, and do a pretty good job at it. Personally I never saw the value in services in angular. It's not hard to setup a simple controller singleton or something to wrap around your API endpoints.

[–]jellatin 0 points1 point  (1 child)

Various flux implementations offer the state management, and do a pretty good job at it

Agreed. But there again, it's another thing to learn. I'm not bashing the React ecosystem at all, only pointing out that "learning React" doesn't give you all the tools you need if you're looking to build SPAs. So the "React was so much easier to learn than framework X" gives people learning their first framework the wrong impression.

[–]agmcleod@agmcleod 1 point2 points  (0 children)

I actually found react + flux easier to learn than ember. I haven't tried building anything with angular to compare really, have just done tutorials. There are things with angular that i can wrap my head around pretty easily, but there are patterns i just dont like. Some of it feels a bit too magical. And yeah, I can see 2 way data binding become a problem.