,
5 tweets,
2 min read
Read on Twitter
"code split across 20 different packages"... a newly generated create-react-app 2.1.5 app that doesn't actually do anything will have 1,568 dependencies.
$ npm ls --parseable | wc -l
[Errors elided. Why does a newly generated app error? -GRB]
1568
$ npm ls --parseable | wc -l
[Errors elided. Why does a newly generated app error? -GRB]
1568
When I write tweets like this, some read it as "Gary hates JS". I like React and prefer it to all alternatives including HTML. I like and use TypeScript. Etc. That doesn't require me to think that "hello world" having 1,568 dependencies containing 1,119,218 LOC is a good idea.
These 1,568 packages maintained (or not!) by many different people are not at all equivalent to something like Visual Studio. news.ycombinator.com/item?id=191960…
Lots of this: "people want small libraries but then they complain that there are too many". Yes. Small libraries *and* few of them. Then you have a chance at building a simple system, not one that's merely "easy" at first glance because someone wrote your config files for you.
This distinction with this terminology has been in the lore since 2011. You should watch the talk! infoq.com/presentations/…
