4 ms·
Unless you create file paths that are so long that they break the default tools of the OS. That’s the point where you went too far.
by kuschku 12y ago
Unless you create file paths that are so long that they break the default tools of the OS. That’s the point where you went too far.
- ossreality 12y agolmao, 256 character max_path is a joke and it's surely not on the fault of node devs who targeted SANE development platforms first.
- pmontra 12y agoOr the OS went too short, so to say. There are two problems here. 1) Windows' limit of 260 characters per path name is incredibly small for a modern OS and that was true many years ago as well. 2) Npm approach relied on well behaved OSes and file systems allowing long path names. It's not future proof because you don't know on which OS and file system you'll need to run, maybe some limited embedded device. Ruby's rvm solved that problem with a single directory level and a gem@version naming scheme.
- kuschku 12y agoExactly. Ruby’s solution will run even on FAT12 (which has only single-level directories), while npm isn’t really compatible. In general, node does this quite often – their memory model also assumes they have infinite memory.