Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

Re:Temporary fork enables Node.js to optionally use the Chak... by pmontra on Wednesday May 13, 2015 @02:55AM (#9537249)

Or 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.

[ Parent | on HN ]

Re:Temporary fork enables Node.js to optionally use the Chak... by kuschku on Friday May 15, 2015 @11:07AM (#9551097)

Exactly. 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.

[ Parent | on HN ]