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 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.
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.
- Svelte (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.
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.
> 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.
Agree 100%