4 ms·
Rails has dependencies, but not like node apps; last time I counted create-react-app vs a new rails app, there was nearly 10x as many distinct maintainers with
by danielheath 4y ago
Rails has dependencies, but not like node apps; last time I counted create-react-app vs a new rails app, there was nearly 10x as many distinct maintainers with access to push new releases to the default dependency tree.
I consider that a better measure of dependency risk than absolute count, since different ecosystems have different ideas about how large a library should be.
- nicoburns 4y agoCreate-react-app isn't really a fair comparison. Create-react-app has ridiculous dependency bloat compared to the norm in the JS ecosystem because it includes every possible option rather than just picking one option in each category. Most serious project using React aren't using create-react-app.
- danielheath 4y agoI’m not really familiar enough to contradict you, beyond saying that - as an outsider - it has by far the most visibility in its space.
- iudqnolq 4y agoFunnily it's now outdated. The brand new react docs don't even mention it: https://react.dev/learn/start-a-new-react-project https://react.dev/learn/start-a-new-react-project > We are currently leaning towards Option 5 ("Turn Create React App into a launcher"). The original goal of Create React App was to provide the best way to start a new React web app for the majority of React users. We like that repurposing it as a launcher explicitly communicates a shift in what we think is best for most new web apps, while at the same time leaving an escape hatch for the older workflows. Unlike Option 3, it avoids the perception that "creating a React app" is somehow deprecated. It acknowledges the reality that a bit of choice is needed, but there are now really great options to choose from. https://github.com/reactjs/react.dev/pull/5487#issuecomment-1409720741 https://github.com/reactjs/react.dev/pull/5487#issuecomment-...