3 ms·

> Coming from the .NET toolchain and expecting a lightweight, easy to start with approach I was yet again totally shocked. > I stopped working when my node mod

> Coming from the .NET toolchain and expecting a lightweight, easy to start with approach I was yet again totally shocked. > I stopped working when my node modules directory topped 60mb and I still hadn't made a data layer. This is cute. I have a 40gb virtual machine with Windows + VS Enterprise and SQL Server, that I have to use to work on a single .NET project that can't be migrated to .NET Core yet. What is 60mb compared to that?

kingcrais_420 8y ago
60MB is a significantly lower amount compared to 40GB, but I don't think it is fair to compare the disk space of an operating system, IDE, and database server to a directory of javascript libraries.
- qudat 8y ago
  If a developer cannot meaningfully work within .NET without an IDE, it absolutely counts. Just like someone on the frontend cannot work without babel or typescript. Those libraries add specialized tooling for the project in question. Instead of downloading a runtime that has a huge std, in JS everything is downloaded on a per-project basis. I cannot speak to .NET, but want to work with python? Bring in one library and it'll top 40MB (e.g. numpy). I don't get why so many people complain about `node_modules` filesize, it's not even an issue to think about.
  - scrollaway 8y ago
    They complain because they're under the impression that everything in node_modules will end up shipped to the browser. It's also more visible. Python libraries are hidden in the environment far from your shell or file manager. So you don't know that your virtualenv weighs 300mb. But node_modules is right there, you can't help but look. In other words it's a complete lack of experience, regardless of how adamant the OP is about their skills.
    - latronic_notron 8y ago
      Exactly. For a while .NET Core also had a folder within the project for third-party NuGet modules, and for a simple web app they would go into the 200mb, and that's without the compiler itself. Now those files live in a hidden folder (or were absorbed by the stdlib), and nobody complains about it anymore. Initiatives like Yarn's plug-and-play [1] would have the side effect of being great marketing for Node.js development. [1] https://github.com/yarnpkg/rfcs/blob/master/accepted/0000-plug-an-play.md https://github.com/yarnpkg/rfcs/blob/master/accepted/0000-pl...
int_19h 8y ago
It sounds like OP was trying to make a beginner-level sample app in Node.js - is your .NET app of the same nature? Judging by the mention of SQL Server, it's not.
- latronic_notron 8y ago
  It's a CRUD app. Nothing special about it. It just happens to use this specific stack.

kingcrais_420 8y ago

60MB is a significantly lower amount compared to 40GB, but I don't think it is fair to compare the disk space of an operating system, IDE, and database server to a directory of javascript libraries.

qudat 8y ago
If a developer cannot meaningfully work within .NET without an IDE, it absolutely counts. Just like someone on the frontend cannot work without babel or typescript. Those libraries add specialized tooling for the project in question. Instead of downloading a runtime that has a huge std, in JS everything is downloaded on a per-project basis. I cannot speak to .NET, but want to work with python? Bring in one library and it'll top 40MB (e.g. numpy). I don't get why so many people complain about `node_modules` filesize, it's not even an issue to think about.
- scrollaway 8y ago
  They complain because they're under the impression that everything in node_modules will end up shipped to the browser. It's also more visible. Python libraries are hidden in the environment far from your shell or file manager. So you don't know that your virtualenv weighs 300mb. But node_modules is right there, you can't help but look. In other words it's a complete lack of experience, regardless of how adamant the OP is about their skills.
  - latronic_notron 8y ago
    Exactly. For a while .NET Core also had a folder within the project for third-party NuGet modules, and for a simple web app they would go into the 200mb, and that's without the compiler itself. Now those files live in a hidden folder (or were absorbed by the stdlib), and nobody complains about it anymore. Initiatives like Yarn's plug-and-play [1] would have the side effect of being great marketing for Node.js development. [1] https://github.com/yarnpkg/rfcs/blob/master/accepted/0000-plug-an-play.md https://github.com/yarnpkg/rfcs/blob/master/accepted/0000-pl...

int_19h 8y ago

It sounds like OP was trying to make a beginner-level sample app in Node.js - is your .NET app of the same nature? Judging by the mention of SQL Server, it's not.

latronic_notron 8y ago
It's a CRUD app. Nothing special about it. It just happens to use this specific stack.