4 ms·
I'm not sure what it is about the node development environment but you are right. I haven't seen such wildly complicated dependency trees in any other language.
by ehnto 8y ago
I'm not sure what it is about the node development environment but you are right. I haven't seen such wildly complicated dependency trees in any other language. Literally hundreds of modules can come together to make even simple applications.
Is there an idiom or ethos in node land that aims for tiny re-usable packages? I am not criticising if there is, just genuinely curious.
I have been writing JS applications for years and it's only since node and npm hit the scene that this has occured.
- Lowkeyloki 8y agoIt might be the Unix philosophy taken to its logical extreme. Everything should do one thing and do it well. So now we have libraries that are literally a single function.
- shittyadmin 8y agoHere's the thing though: You could build this in pure Node and call Windows APIs, Qt, etc and it'd be much, much smaller. But everyone just goes ahead and pulls in Chrome. It's shameful, and the worst part is that I get it - at this point I'm suggesting we go to Electron for a new application at work because it seems like the best maintained UI frameworks with readily available 3rd party components are all web based.