top | item 35661407 (no title) Rimintil | 2 years ago This is due to file system filter [drivers], not the file system. NTFS is perfectly fine and performs well. discuss order hn newest dboreham|2 years ago Hmm. I thought the problem was that NTFS is not particularly fast at file creation. Generally not a problem, except for the folks who wrote the npm tooling which generates 10,000 files in the blink of an eye. Rimintil|2 years ago Yep, I feel (a little) bad for anyone doing node development on Windows (though I probably should feel bad that they're having to dev in JS).But this isn't an "NTFS problem" as you'll have this occur on any filesystem that supports file system filters, like antivirus.
dboreham|2 years ago Hmm. I thought the problem was that NTFS is not particularly fast at file creation. Generally not a problem, except for the folks who wrote the npm tooling which generates 10,000 files in the blink of an eye. Rimintil|2 years ago Yep, I feel (a little) bad for anyone doing node development on Windows (though I probably should feel bad that they're having to dev in JS).But this isn't an "NTFS problem" as you'll have this occur on any filesystem that supports file system filters, like antivirus.
Rimintil|2 years ago Yep, I feel (a little) bad for anyone doing node development on Windows (though I probably should feel bad that they're having to dev in JS).But this isn't an "NTFS problem" as you'll have this occur on any filesystem that supports file system filters, like antivirus.
dboreham|2 years ago
Rimintil|2 years ago
But this isn't an "NTFS problem" as you'll have this occur on any filesystem that supports file system filters, like antivirus.