5 ms·

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 a

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.

SriniK 8y ago
Did you consider http://kubevirt.io/ http://kubevirt.io/ ? It supposed to solve some of these hard limitations.
- pdimitar 8y ago
  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.
lkrubner 8y ago
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-programming-paradigm-that-we-should-get-rid-of http://www.smashcompany.com/technology/docker-protects-a-pro...
- foolzcrow 8y ago
  Why are you such a pussy? You flagged my Hillary Clinton is shit comment. You lost because your ideology is broken trash and I've been a lifelong Democrat so go let more Russians fuck your mom..#snowflake again I'm a lifelong Democrat and I'm going to vote against you
craftyguy 8y ago
Always use / Windows can, surprisingly, handle it just fine.
- JetSpiegel 8y ago
  On interactive uses, sure. But it's not clear cut, some code paths are lower level and bypass that.
  - craftyguy 8y ago
    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 /?
    - testvox 8y ago
      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.
- lardo 8y ago
  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 :(
- mkesper 8y ago
  Never use windows, why should you for development and deployment?

SriniK 8y ago

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

pdimitar 8y ago
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.

lkrubner 8y ago

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-programming-paradigm-that-we-should-get-rid-of http://www.smashcompany.com/technology/docker-protects-a-pro...

foolzcrow 8y ago
Why are you such a pussy? You flagged my Hillary Clinton is shit comment. You lost because your ideology is broken trash and I've been a lifelong Democrat so go let more Russians fuck your mom..#snowflake again I'm a lifelong Democrat and I'm going to vote against you

craftyguy 8y ago

Always use / Windows can, surprisingly, handle it just fine.

JetSpiegel 8y ago
On interactive uses, sure. But it's not clear cut, some code paths are lower level and bypass that.
- craftyguy 8y ago
  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 /?
  - testvox 8y ago
    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.
lardo 8y ago
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 :(
mkesper 8y ago
Never use windows, why should you for development and deployment?