8 ms·

At first I agreed with you; but then I read one of the comments on github that swayed me. "You are the one playing games - calling core parts of Windows like E

by nopar8 12y ago

At first I agreed with you; but then I read one of the comments on github that swayed me. "You are the one playing games - calling core parts of Windows like Explorer "3rd party tools", and suggesting that not supporting long paths is a bug. Microsoft have made it clear repeatedly that non-support for long paths is not a bug, and not something that will change. A package manager creating paths that do not work with the majority of the software written for an OS, then claiming compatibility with the OS, is playing games, at your users expense." At the end of the day Windows wont be the thing changing. haha.

nevi-me 12y ago
I don't follow, should we then rename everything to cryptic, short characters like some people do in MongoDB (as someone suggested using n_m instead of node_modules)? If it works well in other platforms, it's an issue with that specific platform
- nopar8 12y ago
  I think we're arguing different things. I'm more talking semantics.
- rando289 12y ago
  windows has path length limits. Figure out how to live in them, whatever way is best. If that means using cryptic names, then do it. cryptic folder names, while not a good thing, are extremely common in windows.
  - tlrobinson 12y ago
    Or, don't support Windows.
    - rando289 12y ago
      Yes, fine by me.
tlrobinson 12y ago
Microsoft can decide to not call it a bug but that doesn't mean the rest of us don't believe it's a bug.
- CmonDev 12y ago
  In that case Node.js has a huge bug - only natively supporting one messy legacy language (without crap-transpilation).
dbbolton 12y ago
Right, in practical terms it's up to Node to fix this (or go extreme and drop Windows support), but in a more abstract sense I still blame Microsoft for such a glaring design flaw in their software that they are unwilling/unable to fix.

8 ms·

At first I agreed with you; but then I read one of the comments on github that swayed me. "You are the one playing games - calling core parts of Windows like E

by nopar8 12y ago

nevi-me 12y ago
I don't follow, should we then rename everything to cryptic, short characters like some people do in MongoDB (as someone suggested using n_m instead of node_modules)? If it works well in other platforms, it's an issue with that specific platform
- nopar8 12y ago
  I think we're arguing different things. I'm more talking semantics.
- rando289 12y ago
  windows has path length limits. Figure out how to live in them, whatever way is best. If that means using cryptic names, then do it. cryptic folder names, while not a good thing, are extremely common in windows.
  - tlrobinson 12y ago
    Or, don't support Windows.
    - rando289 12y ago
      Yes, fine by me.
tlrobinson 12y ago
Microsoft can decide to not call it a bug but that doesn't mean the rest of us don't believe it's a bug.
- CmonDev 12y ago
  In that case Node.js has a huge bug - only natively supporting one messy legacy language (without crap-transpilation).
dbbolton 12y ago
Right, in practical terms it's up to Node to fix this (or go extreme and drop Windows support), but in a more abstract sense I still blame Microsoft for such a glaring design flaw in their software that they are unwilling/unable to fix.