News for hackers. Stuff that matters.
Re:“Node.js is one of the worst things to happen to the soft... by Sacho on Tuesday August 23, 2016 @07:27AM (#12342808)
> So there's an example of node-specific problem and there doesn't seem to be any impetus surrounding solving it.

??? There's so little impetus around solving it that both sides(npm and Microsoft) have put in significant effort to do it - npm 3 reduced the chance of having a very large path, and preview builds of the .net file api are removing the MAX_PATH limit.

https://github.com/Microsoft/nodejstools/issues/69

https://github.com/Microsoft/nodejs-guidelines/blob/master/w...

Re:“Node.js is one of the worst things to happen to the soft... by zamalek on Tuesday August 23, 2016 @11:36AM (#12344556)
Fair enough, I'd strike-through that quip in my comment if I could. Still, this problem needs a bold/breaking fix. I most likely didn't run into this with my dev-testing because I am on a filesystem with reparse support.