Forums
Thread
Is ReactJS really solving your "View" problems?
Lately there has been som buzz about how senseful React is to creating WebApps. Fundamentally different from jQuery's approach, it provides it's own syntax and abstraction over DOM, so that it's really not easy to reuse well done jQuery Plugins or upcoming WebComponents. With that in mind - does development pay off, having a good "View" architecture , or is time to market and with that reuseability (copy and pasteability) more important to you?
For reference, the two articles I am referring to:
Responses(3)
Well, here is my opinion.
I voted for the 1st option
It really makes sense to use React along with Flux architecture. I won't recommend using React with AngularJS, although some developers claim that it increases the performance. React is already well optimized and performs really well.
The virtual DOM technique is what makes React so fast. Due to virtual DOM it's able to quickly compute the diff and update the part of the UI accordingly. So, there is no reason you should be averse to it.
The Flux architecture is beautiful. It gives your app a solid architecture and thereby helps you avoid writing messy JavaScript code. React and Flux architecture is being widely used in big platforms like Facebook, Instagram etc. So, it's a proven strategy and design pattern. There are also several Node modules available that let you implement Flux architecture without making significant efforts. I would say just go for it, learn it and it will pay off.
We have settled with React+Flux for one of our new projects. Moreover, React apps render on server as well which is a big plus.You don't get this benefit anywhere else.
Michael Brown
I voted for the first option too.
That "React Is A Terrible Idea" post is narrow-minded nonsense. It's major criticism of React seems to be that browsers are improving all the time, so anybody trying to do anything about slow rendering speeds now is really just wasting their time.
That might be true, but IMHO it's the likes of React showing up how crap DOM rendering really is, that will be forcing the browser makers' hands here.
Plus, we all know that Fortune 100 companies always update to the latest browser versions the day that they're released, right? Not one of them still stuck on IE 9 (or worse!) "due to compatibility issues with our existing codebase".