3 ms·
Windows treats you like the product now, it's not your device. Try to defer an update (which takes forever) or dial back the information they get sent. It's jus
by ENGNR 8y ago
Windows treats you like the product now, it's not your device. Try to defer an update (which takes forever) or dial back the information they get sent. It's just not going to happen
Not to mention the constant battle with windows defender, which slows npm installs and webpack compiles to an absolute crawl due to the large number of filesystem requests, won't respect a whitelist, and re-enables itself every 4-24 hours depending on the phase of the moon
- 52-6F-62 8y agoIs this your experience with the Linux subsystem as well, or using Node through PowerShell or Command Prompt?
- thrower123 8y ago> Not to mention the constant battle with windows defender, which slows npm installs and webpack compiles to an absolute crawl due to the large number of filesystem requests, won't respect a whitelist, and re-enables itself every 4-24 hours depending on the phase of the moon I'm not a huge fan of Defender (although it is less like malware than most anti-viruses I've been forced to use), but npm and webpack are not blameless here. It's completely flipping absurd how many tens of thousands of files a medium size front-end project that uses these technologies spawns and kills every time it is rebuilt. I'm tempted to RAM-disk those folders, because even with fast SSDs, IO speed becomes a gating factor in my workflow.
- com2kid 8y agoQuite a few years back, someone did a test compiling a large project on Windows, and on a Linux VM running on that same Windows box, all using the same compiler tool chain. The Linux VM compiled the project faster. :/ The conclusion was that NTFS may have issues with thousands upon thousands of small files. I'd really like to see an updated comparison, it'd be a fun set of benchmarks to run and investigate.