6 ms·
React itself was never a framework, just a library to render user interfaces. Routing, data fetching etc. have always been separate libraries (or built into fra
by kouroshp 2y ago
React itself was never a framework, just a library to render user interfaces. Routing, data fetching etc. have always been separate libraries (or built into frameworks).
- esperent 2y agoThis way of stating things leaves out the central position that React has in any setup. You'll always be using a React routing library, a React data fetching library, a React state management system, and so on.
- TiredOfLife 2y ago> You'll always be using a React routing library, a React data fetching library That's like saying "you will always use js in backend" while ignoring every other backend language.
- floydnoel 2y agodevelopers often want those things, but they are certainly not required. i certainly don’t use a react data fetching library, i just use fetch. i don’t use special react state management, just use redux. i did build a router that works primarily with React in order to support JSX in the components, but it wouldn't be any harder to adapt it to another framework or setup. the problem is exactly the same as those memes making fun of people asking on stack overflow "how do i add two numbers with jQuery?" eg 'how do we add two numbers with React' the problem is there are always new developers making silly mistakes, and making that an indictment of some technology is a fallacy.
- deleted 2y ago[deleted]
- EdwardDiego 2y agoIt wasn't like that when it first came out, from my experiments with it when it was first released.