I mean, and correct me if I'm wrong, Node "fs" module is now optimized for Windows and not Linux, right? Personally I'd like to see that module not using the thread pool...
> I mean, and correct me if I'm wrong, Node "fs" module is now optimized > for Windows and not Linux, right? > Personally I'd like to see that module not using the thread pool...
> Thanks,
> -Pedro
The fs module is not optimized for windows. On windows we basically do the same thing as on unix, doing filesystem operations in a thread pool. In theory windows supports real asynchronous file i/o but there were too many problems with it.
>> I mean, and correct me if I'm wrong, Node "fs" module is now optimized >> for Windows and not Linux, right? >> Personally I'd like to see that module not using the thread pool...
>> Thanks,
>> -Pedro
> The fs module is not optimized for windows. On windows we basically do > the same thing as on unix, doing filesystem operations in a thread > pool. > In theory windows supports real asynchronous file i/o but there were > too many problems with it.
On Dec 9, 2:32 am, Mikeal Rogers <mikeal.rog...@gmail.com> wrote:
> Did file watching at least get moved to native or are we still just polling in the thread pool?
It did, but only fs.watch() and not watchFile().
I also expect there to be some bugs (please report them). Features and APIs wildly differ across platforms so it is very hairy to get right. Also I should say that only local filesystems are reliable, it will probably fail silently on nfs drives.