5 ms·

React is such BS. Its sole purpose for existing is to make simple tasks unnecessarily complicated.

by amgin3 10y ago

codez4lyfe 10y ago
lol
castis 10y ago
Would you like to share any reasons you believe that? Or at least which part you find unnecessarily complicated? React exists out of a need to organize a complex system of interactions. Unless you understand what it's like to have to reel that sort of thing in, it's not going to be easy to wrap your head around quickly.
dump121 10y ago
After using it in couple of projects, we see it as making complex tasks really intuitive. Maybe you are using it for some wrong problem.
- k__ 10y ago
  I had the same feeling. Coming from ExtJS and Ember, React felt rather simple. But Redux is a whole nother story :(
  - Sacho 10y ago
    Have you thought about using MobX instead? I think Redux's "complications" stem from guiding you towards a certain set of principles and ways of coding without giving you the tools to commit to those principles and ways of coding. Particularly, the way you compose reducers and the way you expose actions is manual and very boilerplate-ish. Mark Erikson hosts a wonderful page full of redux ecosystem links, and here you can see all the tools to allow you to write and compose reducers - https://github.com/markerikson/redux-ecosystem-links/blob/master/reducers.md https://github.com/markerikson/redux-ecosystem-links/blob/ma... so clearly there was something missing there. Redux as an idea I found very simple yet interesting. Watching Dan Abramov's series on building a Redux-lite from scratch helped changed my way of approaching how I build web apps. However, using Redux in the mundane, daily sense was riddled with little practical niggles that were never really answered by the fairly minimalistic library, so I ended up with a kind of feeling that Redux kind of required me to "know" how to write good code before I commit to using it... Meanwhile MobX seems to map to my mental model and all the modes of "mutation" that I'm already used to and have experience in, while also essentially introducing the same ideas as Redux.
    - purplerabbit 10y ago
      Mobx is far more intuitive (and fun) than Redux. It truly enables you to focus on features rather than concepts. Mobx also frees you from the "Redux architecture", which I found to be difficult and contrived...
      - jbeja 10y ago
        Mobx? Seriously? Another unqualified one to have a opinion on the matter.
    - ergothus 10y ago
      I'm currently in the process of migrating a decently large React app from poorly written React/Flux to (hopefully) better written React/Redux, and I'm definitely feeling the lack of...useful examples. A ToDo list or showing lists of users from Github just doesn't cover the realistic complex problems well. Thus, when I encounter one of those problems, and Google fails me, I have to take a stab at it...and likely recreate the not-best-architectures of those that have done the same before me. I'm still happy with Redux so far - the patterns it encourages is at least an improvement over the code from before, but I can't shake the the feeling that there are basic mistakes I'm making because I only have a handful of best practices goals.
      - acemarke 10y ago
        Hi. My React/Redux links list [0] has a category for Redux architecture and best practices [1], with a ton of good info. Also, the "Redux Tutorials" category has a "Project-Based Tutorials" section [2], which points to a number of tutorials that try to build _something_ in the process of teaching. Many of those tutorials are quite a bit more complex than yet another TodoMVC example. To pick out two specific examples: - "Building a Simple CRUD App with React + Redux" [3] is an 8-part series that demonstrates building a CRUD app, including routing, AJAX calls, and the various CRUD aspect - My own "Practical Redux" series [4] tries to demonstrate a number of intermediate to advanced React and Redux concepts in the context of a semi-meaningful-ish sample app. Finally, my Redux addons list has a section listing a number of interesting React+Redux apps [5], both purpose-built examples and real world projects. Hopefully that gives you some useful examples to work with. I'd also encourage you to drop by the Reactiflux chat channels on Discord to ask questions and get feedback, at https://www.reactiflux.com https://www.reactiflux.com . Feel free to ping me on there! [0] https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links [1] https://github.com/markerikson/react-redux-links/blob/master/redux-architecture.md https://github.com/markerikson/react-redux-links/blob/master... [2] https://github.com/markerikson/react-redux-links/blob/master/redux-tutorials.md#project-based-tutorials https://github.com/markerikson/react-redux-links/blob/master... [3] http://www.thegreatcodeadventure.com/building-a-simple-crud-app-with-react-redux-part-1/ http://www.thegreatcodeadventure.com/building-a-simple-crud-... [4] http://blog.isquaredsoftware.com/series/practical-redux http://blog.isquaredsoftware.com/series/practical-redux [5] https://github.com/markerikson/redux-ecosystem-links/blob/master/apps-and-examples.md https://github.com/markerikson/redux-ecosystem-links/blob/ma...
  - acemarke 10y ago
    Hi! Got a couple pointers for you. First, my React/Redux links list [0] has links to many Redux tutorials of various kinds, as well as dozens of articles on Redux architecture, best practices, and useful techniques. Second, if you've got questions, the Reactiflux chat channels on Discord are a great place to hang out, ask questions, and learn. I'm an admin, and hang out there evenings US time, but there's always plenty of people happy to talk and answer questions. The invite link is at https://www.reactiflux.com https://www.reactiflux.com . Please feel free to ping me there if there's anything I can do to help! [0] https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links
- jbeja 10y ago
  You're unqualified to actual have an opinion on the matter.
YCode 10y ago
This argument has been applied to virtually every framework or library at some point; the points and counterpoints rarely change and the result is inevitably to use right tool for your type AND scale of problem. FWIW React's purpose is the opposite of what you said; it aims to make complex UI tasks simple by allowing you to compartmentalize your UI into isolated components. If your UI isn't that complex or your application has very little state to manage then I could see how React would be overkill.
sctb 10y ago
Please don't post snarky one-liners here.
huangc10 10y ago
I think you're referring to the concept of Javascript Fatigue (which I found was quite funny...). Check out this article: https://medium.com/@ericclemmons/javascript-fatigue-48d4011b6fc4#.le2jsejez https://medium.com/@ericclemmons/javascript-fatigue-48d4011b... Maybe it'll change your mind

React is such BS. Its sole purpose for existing is to make simple tasks unnecessarily complicated.

by amgin3 10y ago

React is such BS. Its sole purpose for existing is to make simple tasks unnecessarily complicated.

codez4lyfe 10y ago

lol

castis 10y ago

Would you like to share any reasons you believe that? Or at least which part you find unnecessarily complicated? React exists out of a need to organize a complex system of interactions. Unless you understand what it's like to have to reel that sort of thing in, it's not going to be easy to wrap your head around quickly.

dump121 10y ago

After using it in couple of projects, we see it as making complex tasks really intuitive. Maybe you are using it for some wrong problem.

k__ 10y ago
I had the same feeling. Coming from ExtJS and Ember, React felt rather simple. But Redux is a whole nother story :(
- Sacho 10y ago
  Have you thought about using MobX instead? I think Redux's "complications" stem from guiding you towards a certain set of principles and ways of coding without giving you the tools to commit to those principles and ways of coding. Particularly, the way you compose reducers and the way you expose actions is manual and very boilerplate-ish. Mark Erikson hosts a wonderful page full of redux ecosystem links, and here you can see all the tools to allow you to write and compose reducers - https://github.com/markerikson/redux-ecosystem-links/blob/master/reducers.md https://github.com/markerikson/redux-ecosystem-links/blob/ma... so clearly there was something missing there. Redux as an idea I found very simple yet interesting. Watching Dan Abramov's series on building a Redux-lite from scratch helped changed my way of approaching how I build web apps. However, using Redux in the mundane, daily sense was riddled with little practical niggles that were never really answered by the fairly minimalistic library, so I ended up with a kind of feeling that Redux kind of required me to "know" how to write good code before I commit to using it... Meanwhile MobX seems to map to my mental model and all the modes of "mutation" that I'm already used to and have experience in, while also essentially introducing the same ideas as Redux.
  - purplerabbit 10y ago
    Mobx is far more intuitive (and fun) than Redux. It truly enables you to focus on features rather than concepts. Mobx also frees you from the "Redux architecture", which I found to be difficult and contrived...
    - jbeja 10y ago
      Mobx? Seriously? Another unqualified one to have a opinion on the matter.
  - ergothus 10y ago
    I'm currently in the process of migrating a decently large React app from poorly written React/Flux to (hopefully) better written React/Redux, and I'm definitely feeling the lack of...useful examples. A ToDo list or showing lists of users from Github just doesn't cover the realistic complex problems well. Thus, when I encounter one of those problems, and Google fails me, I have to take a stab at it...and likely recreate the not-best-architectures of those that have done the same before me. I'm still happy with Redux so far - the patterns it encourages is at least an improvement over the code from before, but I can't shake the the feeling that there are basic mistakes I'm making because I only have a handful of best practices goals.
    - acemarke 10y ago
      Hi. My React/Redux links list [0] has a category for Redux architecture and best practices [1], with a ton of good info. Also, the "Redux Tutorials" category has a "Project-Based Tutorials" section [2], which points to a number of tutorials that try to build _something_ in the process of teaching. Many of those tutorials are quite a bit more complex than yet another TodoMVC example. To pick out two specific examples: - "Building a Simple CRUD App with React + Redux" [3] is an 8-part series that demonstrates building a CRUD app, including routing, AJAX calls, and the various CRUD aspect - My own "Practical Redux" series [4] tries to demonstrate a number of intermediate to advanced React and Redux concepts in the context of a semi-meaningful-ish sample app. Finally, my Redux addons list has a section listing a number of interesting React+Redux apps [5], both purpose-built examples and real world projects. Hopefully that gives you some useful examples to work with. I'd also encourage you to drop by the Reactiflux chat channels on Discord to ask questions and get feedback, at https://www.reactiflux.com https://www.reactiflux.com . Feel free to ping me on there! [0] https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links [1] https://github.com/markerikson/react-redux-links/blob/master/redux-architecture.md https://github.com/markerikson/react-redux-links/blob/master... [2] https://github.com/markerikson/react-redux-links/blob/master/redux-tutorials.md#project-based-tutorials https://github.com/markerikson/react-redux-links/blob/master... [3] http://www.thegreatcodeadventure.com/building-a-simple-crud-app-with-react-redux-part-1/ http://www.thegreatcodeadventure.com/building-a-simple-crud-... [4] http://blog.isquaredsoftware.com/series/practical-redux http://blog.isquaredsoftware.com/series/practical-redux [5] https://github.com/markerikson/redux-ecosystem-links/blob/master/apps-and-examples.md https://github.com/markerikson/redux-ecosystem-links/blob/ma...
- acemarke 10y ago
  Hi! Got a couple pointers for you. First, my React/Redux links list [0] has links to many Redux tutorials of various kinds, as well as dozens of articles on Redux architecture, best practices, and useful techniques. Second, if you've got questions, the Reactiflux chat channels on Discord are a great place to hang out, ask questions, and learn. I'm an admin, and hang out there evenings US time, but there's always plenty of people happy to talk and answer questions. The invite link is at https://www.reactiflux.com https://www.reactiflux.com . Please feel free to ping me there if there's anything I can do to help! [0] https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links
jbeja 10y ago
You're unqualified to actual have an opinion on the matter.

YCode 10y ago

This argument has been applied to virtually every framework or library at some point; the points and counterpoints rarely change and the result is inevitably to use right tool for your type AND scale of problem. FWIW React's purpose is the opposite of what you said; it aims to make complex UI tasks simple by allowing you to compartmentalize your UI into isolated components. If your UI isn't that complex or your application has very little state to manage then I could see how React would be overkill.

sctb 10y ago

Please don't post snarky one-liners here.

huangc10 10y ago

I think you're referring to the concept of Javascript Fatigue (which I found was quite funny...). Check out this article: https://medium.com/@ericclemmons/javascript-fatigue-48d4011b6fc4#.le2jsejez https://medium.com/@ericclemmons/javascript-fatigue-48d4011b... Maybe it'll change your mind