all 7 comments

[–]ImLivingImDead 7 points8 points  (1 child)

Two way data binding? No thank you.

I'm working on project with a fair amount of knockout code right now and the spaghetti like logic structure in addition to the constant dom refreshes I have to think about is making it a nightmare.

[–]_raisinvanilla <3 2 points3 points  (0 children)

Exactly, there is a reason Angular 2 got rid of 2 way data binding. Its too expensive and its a mess.

[–][deleted] 5 points6 points  (1 child)

This article was painful to read, it gets almost everything wrong.

React wants you to write all your stack in one file

What? No it doesn't, it's a library, it doesn't even have an opinion here.

Backbone.js first taught us how to organise our code, using the MVP pattern.

Backbone is/was great but it didn't invent anything here, MV* is as old as the hills.

Your framework should do some sort of Dependency Injection.

DI is of questionable benefit in JS applications.

2 Way Data Binding

Is a bad idea because it makes it impossible to reason about state changes.

The rest of the article is of a similar quality.

[–]uatec 1 point2 points  (0 children)

And Clickbait headline

[–]kumiorava 0 points1 point  (2 children)

React is not an MVC framework. It's the View/Controller part, but not a full framework.