Hacker News Reader

Comment by testvox | Hacker News Reader

Sorry but this article implies that containers can solve issues like the difference between path separators on Windows and Linux. They can't even solve issues arising from differences in kernal versions, not to mention operating systems.

View on HN

Nor does Docker protect against such obvious things as differences in versions of base images. Check out the Slack dialogue at the end of this:

http://www.smashcompany.com/technology/docker-protects-a-pro...

Did you consider http://kubevirt.io/ ? It supposed to solve some of these hard limitations.

This can work, but stacking framework on top of the framework is what made the classic application servers undesirable and a horrible mess to begin with.

Observing similar patterns creeping in the Kubernetes culture and ecosystem does not inspire optimism in a side observer like myself.

Always use /

Windows can, surprisingly, handle it just fine.

On interactive uses, sure. But it's not clear cut, some code paths are lower level and bypass that.

Yea I guess most of my uses have been in things like python (e.g. open() and as.*). Got any examples of code paths that bypass that check and fail if you use /?

I think they are wrong and actually it's the opposite problem. Some applications and libraries that do their own path mangling on Windows will choke if you give them a /. The win32 file I/O API handles them correctly.

I spent two hours scratching my head today because I had put

  "/path/to/thing/**"

in a nuspec file instead of

  "\path\to\thing\**"

The backslash was escaping the wildcard characters :(

Never use windows, why should you for development and deployment?

Reply on news.ycombinator.com