Yes but it does alot of stuff.
It's not surprising or concerning.
That's what it takes to get modern things built - lots of other things.
It's not surprising or concerning.
That's what it takes to get modern things built - lots of other things.
In fact, the 1.5k dependencies in this example is a drop in the bucket when you consider all the dependencies that your react app needs to do anything useful (http, dns, tcp, ip, browsers, OS’s, et cetera).
I’m not defending React here, I don’t know enough about it, I’m just saying 1.5k dependencies for a hello world app might be bad, but it depends on the details.
Similar case with babel and webpack, that each plugins (and loader) is a separate dependency. I don't know if it's more efficient or modular for development, but it is surely bloat the packages.
The whole brogrammer culture of "throw another library onto the fire" is the reason that simple programs require crazy amounts of computing power.
It's not just JavaScript that has dependencies - everything does.
It’s not the concept of dependencies that’s at fault, it’s the number of them proportional to the task.
Yet, we don't just eat dirt off the street because even when we eat the usual food, there's always some dirt in it.
A ton of websites out there do the latter.
I don't need to do assembly language programming because the tools I have (that are built on top of it) are actually good. Unlike those in JS land.