4 ms·

I don't know about you, but I don't use react because I don't know how to use it. I think it would be more interesting to read about people who know how to use

I don't know about you, but I don't use react because I don't know how to use it. I think it would be more interesting to read about people who know how to use it, have used it, but now choose not to.

gnarbarian 7y ago
The first step to knowing how to use something is using it.
- throwaway66666 7y ago
  I was mostly trying to make a civil snark. That the author of the artile seems to be making these comments as an "outsider" and has not actually used it in real life projects. Therefore I am a bit confused as to where they are coming from. As for me I 'll probably give react a try when it aligns with the tasks and scope of my work, nothing against it.
2trill2spill 7y ago
> I think it would be more interesting to read about people who know how to use it, have used it, but now choose not to. I use react all the time, particularly at my job, and it's not that I choose not to use it now, I just choose not to use react for some projects. For simple UI I reach for server side html templating, with a sprinkle of CSS and Vanilla JS. For UI library code that could be shared with React and non react projects, again I use vanilla js. For big complex UI like a dashboard with graphs and charts, and bunch of options and nobs, etc. I will use something like React. There's a time and place where each tool shines or is the better choice.
- scarface74 7y ago
  Well I used plain JS and precompiled Handlebars templates for one project that I really wanted to keep lightweight.
ng12 7y ago
> I think it would be more interesting to read about people who know how to use it, have used it, but now choose not to. I suspect you won't find many people in this camp. I know a great many Angular->React converts, but very, very few lapsed React devs.
- gotfork 7y ago
  As an Angular developer I would be interested in reading some Angular->React conversion stories. I've dabbled in React a few times but it never felt compelling enough to switch, but maybe I missed the good stuff.
  - nestorherre 7y ago
    You should try Vue. I tried to use React a couple of times and never got the hang of it. With Vue however, you could say it was love at first sight (and I've heard some other people say the same)
- cam-stitt 7y ago
  I'm one of the people in that camp. I loved React, and still think it's a fantastic tool. A few things that have made me move on: - Svelte (https://svelte.dev https://svelte.dev) - People thinking Redux is brilliant. It's good, but it's a far too complex system to simply manage state. I'm aware this isn't React, but I have worked on very few React projects that don't have Redux - Run-time load. Back to Svelte. It's inspired me to remove as much run-time work as possible. - API complexity. The React API has exploded over the last year or two. Hooks, memo, portals, error boundaries. Most of them are clever solutions, but are only required due to the limitations of React.
  - ng12 7y ago
    I though svelte was interesting until I read a recent article where they introduced that `$:` label. It seemed like a very poorly thought out approach to me. That said, I honestly don't think I'll ever go back to using a framework with templates. My distaste for them has only gotten stronger the more I use React. > People thinking Redux is brilliant Redux is good as long as you understand what it's good for and only use it when it buys you something. My default recommendation is to not use a state library until you find you need one.

gnarbarian 7y ago

The first step to knowing how to use something is using it.

throwaway66666 7y ago
I was mostly trying to make a civil snark. That the author of the artile seems to be making these comments as an "outsider" and has not actually used it in real life projects. Therefore I am a bit confused as to where they are coming from. As for me I 'll probably give react a try when it aligns with the tasks and scope of my work, nothing against it.

2trill2spill 7y ago

> I think it would be more interesting to read about people who know how to use it, have used it, but now choose not to. I use react all the time, particularly at my job, and it's not that I choose not to use it now, I just choose not to use react for some projects. For simple UI I reach for server side html templating, with a sprinkle of CSS and Vanilla JS. For UI library code that could be shared with React and non react projects, again I use vanilla js. For big complex UI like a dashboard with graphs and charts, and bunch of options and nobs, etc. I will use something like React. There's a time and place where each tool shines or is the better choice.

scarface74 7y ago
Well I used plain JS and precompiled Handlebars templates for one project that I really wanted to keep lightweight.

ng12 7y ago

> I think it would be more interesting to read about people who know how to use it, have used it, but now choose not to. I suspect you won't find many people in this camp. I know a great many Angular->React converts, but very, very few lapsed React devs.

gotfork 7y ago
As an Angular developer I would be interested in reading some Angular->React conversion stories. I've dabbled in React a few times but it never felt compelling enough to switch, but maybe I missed the good stuff.
- nestorherre 7y ago
  You should try Vue. I tried to use React a couple of times and never got the hang of it. With Vue however, you could say it was love at first sight (and I've heard some other people say the same)
cam-stitt 7y ago
I'm one of the people in that camp. I loved React, and still think it's a fantastic tool. A few things that have made me move on: - Svelte (https://svelte.dev https://svelte.dev) - People thinking Redux is brilliant. It's good, but it's a far too complex system to simply manage state. I'm aware this isn't React, but I have worked on very few React projects that don't have Redux - Run-time load. Back to Svelte. It's inspired me to remove as much run-time work as possible. - API complexity. The React API has exploded over the last year or two. Hooks, memo, portals, error boundaries. Most of them are clever solutions, but are only required due to the limitations of React.
- ng12 7y ago
  I though svelte was interesting until I read a recent article where they introduced that `$:` label. It seemed like a very poorly thought out approach to me. That said, I honestly don't think I'll ever go back to using a framework with templates. My distaste for them has only gotten stronger the more I use React. > People thinking Redux is brilliant Redux is good as long as you understand what it's good for and only use it when it buys you something. My default recommendation is to not use a state library until you find you need one.