4 ms·

Not everything has to be built with React, and the size of it is orthoganal to the technology. If fact, huge projects are likely to suffer from using React, be

by rimliu 6y ago

Not everything has to be built with React, and the size of it is orthoganal to the technology. If fact, huge projects are likely to suffer from using React, because virtual DOMs get out of hand and a lot of resources a wasted by building and rebuilding VDOM and looking for the changes. Also, for some reason, React brings a lot of cargo-culting. Many don't stop to thing whether they should even if they can. They bring React, then they bring Redux, then all the rest is being dragged in and you get multi MB bundles for some truly trivial purposes. Of course, that's more on developers than on React, but it happens way to often. And for some reason just bringing React and Co. is not enough, it usually ends up in some imressive architecture astronautics. At the end you have a project that is big, but slow and still impossible to understand because the levels of indirection are off the charts.

deleted 6y ago
[deleted]
varrock 6y ago
I'm not going to say you're wrong, because I don't have claim to back mine up, either. So, this is for the sake of discussion. The sentiment that everybody reaches for Redux is tired, in my opinion. After following many in the web development community and keeping up with online forums such as this, it's fairly clear to me that people have moved on from the heavy armor previously associated with React if they have a choice. For instance, people learned that they were using Redux for prop drilling, which led to many switching over to the context API natively from React. Another good example is Gatsby, for those who realized they have a static site and would like to address the SEO issues associated with a SPA. Also, a lot of times, companies adopted React and Redux before the inception of these new, more powerful libraries that are obvious choices on the ground as of August 2020. But, have fun refactoring your entire client side state seamlessly if you're tracking state more sophisticated than the status of the application sidebar.
koonsolo 6y ago
So what do you suggest how huge projects should display data on a single page web app? MVC? MVVM? Just hack things in like the olden days, without any structure?

by rimliu 6y ago

deleted 6y ago

[deleted]

varrock 6y ago

I'm not going to say you're wrong, because I don't have claim to back mine up, either. So, this is for the sake of discussion. The sentiment that everybody reaches for Redux is tired, in my opinion. After following many in the web development community and keeping up with online forums such as this, it's fairly clear to me that people have moved on from the heavy armor previously associated with React if they have a choice. For instance, people learned that they were using Redux for prop drilling, which led to many switching over to the context API natively from React. Another good example is Gatsby, for those who realized they have a static site and would like to address the SEO issues associated with a SPA. Also, a lot of times, companies adopted React and Redux before the inception of these new, more powerful libraries that are obvious choices on the ground as of August 2020. But, have fun refactoring your entire client side state seamlessly if you're tracking state more sophisticated than the status of the application sidebar.

koonsolo 6y ago

So what do you suggest how huge projects should display data on a single page web app? MVC? MVVM? Just hack things in like the olden days, without any structure?