3 ms·
Next and React have gotten way too complicated. I don't want to read twelve pages of documentation to understand how to understand the rest of the documentation
by TechBro8615 3y ago
Next and React have gotten way too complicated. I don't want to read twelve pages of documentation to understand how to understand the rest of the documentation.
I've been coding in React for 6 years and in Next for 3 years. My next project will be in Vue.
- jer0me 3y agoYour nuxt project will be Vue?
- jjdeveloper 3y agogood correction
- Solvency 3y agoSo, what's up with this. How it go from: Javascript isn't sufficient... to React/Vue aren't sufficient... to Next/Nuxt are <insufficient? too complicated?> Why didn't the bandwagon just end at the first layer of frameworks?
- paulddraper 3y agoWhy?
- TechBro8615 3y ago> Next and React have gotten way too complicated. Because I'm fed up with all the unnecessary complexity, and I want to try Vue because it looks a lot less complex, and I've already had a positive experience in the ecosystem with Vite and Vitest.
- paulddraper 3y agoI mean.... This just sounds like novelty. You could keep using the react you've always liked?
- TechBro8615 3y agoYeah, it's a good point, and I'll continue to do that on my stable projects. But for a new project I'd like to try Vue, because I don't like the direction React is moving. In five years the "React I like" might not be available or widely practiced. You're right that Vue will be a novelty - that's what I'm saying: React has jumped the shark to the point that it's now worth trying something for its novelty, because it just might be better.
- CharlieDigital 3y agoIn general, any model that uses fine grained reactivity (Vue, Preact, Solid, Svelte) will be more "forgiving" then one that uses coarse grained reactivity (React) because it triggers smaller component tree updates. This tends to reduce certain classes of bugs like side effects from unexpected re-renders and performance issues like over rendering. The thing with React and Next is that it's great if your team is relatively homogeneous in terms of skill and experience or you have strong systems in place to enforce practices. However, the render cycle of React and the provider pattern is prone to bugginess otherwise. A firsthand example is Algolia's React components. Look at the GH issues. We ran into tons of issues related to unexpected redraws.
- paulddraper 3y agoIf re-renders are causing bugs, you are 100% holding the tool wrong Like having data corruption issues from GET requests. --- I prefer explicit, but if implicit fine grained reactivity is the sole point of concern, you might be interested in React+MobX.
- CharlieDigital 3y agoEvery React team I've worked with has held the tool wrong because on every project I've been on in 3 VC backed startups, I've had to track down unintended side effects. MobX and Valtio create an illusion of fine-grained reactivity but do not change the underlying render cycle of React itself.