3 ms·
> A manager bought into "react everywhere" hype ...that actually exists? Seems crazy. > My experience with React has not been good. Certainly from your story
by DougBTX 9y ago
> A manager bought into "react everywhere" hype
...that actually exists? Seems crazy.
> My experience with React has not been good.
Certainly from your story it sounds like you had a bad experience, but it seems to be in the "had a bad experience with a hammer, terrible for hammering in screws" type of experience.
- ravenstine 9y agoWhy else would we have stuff like this? https://github.com/Izzimach/react-three https://github.com/Izzimach/react-three As if ThreeJS is too hard or cumbersome without React. Or this: https://github.com/FormidableLabs/react-game-kit https://github.com/FormidableLabs/react-game-kit Or this: https://www.npmjs.com/package/react-audio https://www.npmjs.com/package/react-audio (a relatively unknown library, but it's surprising how often projects will import packages like this) I generally do what I can to avoid software snobbery, but it's examples like those that really cause me to scratch my head and exclaim "Why?" React makes sense when you actually have a DOM to deal with, but as soon as you start trying to write something that goes beyond that model, well, I really don't get you. ("you" being rhetorical) Generally, though, I think a lot of junior programmers or those new to React get very enthusiastic about it and try to solve whatever problem they can with a tool that works well for them, and that does speak quite a bit to how good React is. In general, I would avoid using React for things it was not designed for.