React Is A Terrible Idea

added by JavaScript Kicks
3/13/2015 2:03:50 PM

2853 Views

There's been a lot of excitement lately about React. React seems to have bumped Angular from the top of the hippest-framework mountain. This is unfortunate, because both of these frameworks are bad for your application's health. They're also bad for the entire software industry. For new applications, please, for the love of all things open, use Web components instead.


4 comments

Paul Wheeler
3/14/2015 8:07:18 PM
I don't know when I've read an article about JavaScript frameworks I've agreed with more. The future of JavaScript frameworks should be small composable libraries that extend the native capabilities of current browsers and provide polyfills where necessary.

Andrew Robbins
3/15/2015 8:45:39 PM
I'm glad someone else is speaking out more with regards to the separation of concerns in React. They bring a lot of valuable ideas to the table, but this is something that's a deal breaker for many people IMO.

Ofer Zelig
3/16/2015 2:23:04 AM
I started reading it with a pessimistic attitude (meaning: React IS good but let's see what this guy rants about) and ended reading it appreciating this guy and his argument much more. Note taken for any possible future consideration whether to use React or not.

Robert Greyling
3/16/2015 4:08:19 PM
Just like you @oferzelig - I too approached this one with a fair bit of skeptisicm just waiting to the Troll to bite. I'm pretty sure @dyoder has taken a fair bit of flack for his choice of title, and perhaps it is a bit strongly worded, but I think the meat of the article and the main points are actually something that most developers should actually read and consider. I think you're spot on @paulwheeler - embrace and extend! I certainly wasn't considering a lot of what he mentioned before, but I can agree I've had that feeling of "code smell" about one of my latest projects (react) for a while now as it's grown more and more, and often I wonder if I'm slowdy building a ball of mud here? Maybe @dyoder has some concrete examples he can put in his next post that can highlight the issue more clearly for those who are willing to take note...