3 ms·

React doesn't suffer from this. It's React Native.

notJim 6y ago
Interesting, you are right AFAICT (react has numerous packages and I'm not totally sure how they relate). http://npm.anvaka.com/#/view/2d/react http://npm.anvaka.com/#/view/2d/react http://npm.anvaka.com/#/view/2d/react-dom http://npm.anvaka.com/#/view/2d/react-dom
ricardobeat 6y ago
In theory, that is. Since it doesn't include batteries, the controller, the wheels, or the antenna you're gonna end up bringing a ton of dependencies yourself to cover the missing parts (animation, state management, routing etc). Plus you're not seeing the dev dependencies, a more apt comparison would be to create-react-app.
- Silhouette 6y ago
  Since it doesn't include batteries, the controller, the wheels, or the antenna you're gonna end up bringing a ton of dependencies yourself to cover the missing parts (animation, state management, routing etc). Or not. I've worked on plenty of applications that had few if any dependencies for those things. I'm sure many others have too. In some cases that was because we didn't need that particular functionality. Routing has little value if you're building an in-house SPA that always starts from the same dashboard anyway, for example. In other cases, it's because we're programmers and don't import entire library ecosystems to do what we could do ourselves with a few lines of code or some APIs that are already supported by all modern browsers anyway. I liked React when it first arrived, because it was a tool that was that did one useful job and did it reasonably well. I dislike the direction it's taken more recently, because it now seems to be trying to do several jobs and not doing most of them very well at all. I understand that this is partly because of the way some developers coerced React into doing things it wasn't really suitable for and the React dev team have been responding to that, but I still think value has been lost in that process.

Interesting, you are right AFAICT (react has numerous packages and I'm not totally sure how they relate). http://npm.anvaka.com/#/view/2d/react http://npm.anvaka.com/#/view/2d/react http://npm.anvaka.com/#/view/2d/react-dom http://npm.anvaka.com/#/view/2d/react-dom

ricardobeat 6y ago

In theory, that is. Since it doesn't include batteries, the controller, the wheels, or the antenna you're gonna end up bringing a ton of dependencies yourself to cover the missing parts (animation, state management, routing etc). Plus you're not seeing the dev dependencies, a more apt comparison would be to create-react-app.

Silhouette 6y ago
Since it doesn't include batteries, the controller, the wheels, or the antenna you're gonna end up bringing a ton of dependencies yourself to cover the missing parts (animation, state management, routing etc). Or not. I've worked on plenty of applications that had few if any dependencies for those things. I'm sure many others have too. In some cases that was because we didn't need that particular functionality. Routing has little value if you're building an in-house SPA that always starts from the same dashboard anyway, for example. In other cases, it's because we're programmers and don't import entire library ecosystems to do what we could do ourselves with a few lines of code or some APIs that are already supported by all modern browsers anyway. I liked React when it first arrived, because it was a tool that was that did one useful job and did it reasonably well. I dislike the direction it's taken more recently, because it now seems to be trying to do several jobs and not doing most of them very well at all. I understand that this is partly because of the way some developers coerced React into doing things it wasn't really suitable for and the React dev team have been responding to that, but I still think value has been lost in that process.