3 ms·
React itself is already pretty simple if you ignore all the extraneous tooling. The core API is just about a dozen lifecycle methods.
by pdog 11y ago
React itself is already pretty simple if you ignore all the extraneous tooling. The core API is just about a dozen lifecycle methods.
- recursive 11y agoIf you ignore the tooling, then you can't use JSX. If you can't use JSX, then I don't think React is that useful.
- k__ 11y agohave you looked into hyperscript and the hyperscript-helpers? there are versions that work with react.
- spriggan3 11y agoYou can't really code in React professionally if you ignore all the tooling around it, the pipelines , the JSX, the flux/redux/... and all that stuffs. It's like saying "C is pretty simple if you ignore gcc macros,make, autoconf, automake, autogen, pkg-config, ld , and all that stuff". You cant. All these dependencies are necessary and managing them constitute at least half the amount of time spent working with C. Same thing with React. So you pretty much end up with the same level of complexity as more complicated solutions in the real world context.
- KurtMueller 11y agoHaven't ignored JSX, but other than that, I use React in a professional context with the same tooling I use for jQuery.
- thkim 11y agoThat extraneous tooling killed React for me. React itself is simple and easy, I agree with that. But getting things wired up so that you can develop a real application? I think I lost a good day or two on it. Even after I was set up, honestly there were a lot of tweaks left such that I didn't really get to where I wanted to be. Also I can't really see where things might break down in between. It's enough to be frustrated with the code itself, let alone getting bogged down in a long, incomprehensible path along the build pipeline.
- KurtMueller 11y agoI've always thought of React itself as just one step up from jQuery. You don't need to use a router or flux to get use out of it.