←back to thread

535 points raddad | 3 comments | | HN request time: 0.653s | source
Show context
typon ◴[] No.11389194[source]
This might be the most exciting news I've heard in a long time. Being able to use Visual Studio and .NET for web development while using zsh and all the other Linux tools? Dreamland.
replies(3): >>11389261 #>>11389399 #>>11389628 #
Karunamon ◴[] No.11389399[source]
Serious, non-snarky question:

What does this give you that you would not already have with cygwin? The latter installs .exe versions of the usual command line utils, and I'm almost certain ZSH and the others you speak of are included.

I do not understand the practical implications of this move by Canonical/MS other than PR - what's actually changing from a user/dev standpoint?

replies(4): >>11389536 #>>11389555 #>>11389929 #>>11391019 #
metafex ◴[] No.11389555[source]
Cygwin is and always will be only an emulation-layer, never the real deal. For most day-to-day things it works perfectly, but when you run into some corner-case, most of the time you are out of luck.

My only real problem with Cygwin is, that it misses a command-line package manager. If they could adopt pacman for package management like MSYS2 does, I'd be a happy camper.

edit: To deploy Cygwin based applications you need to get a commercial license from RedHat (if it's not FOSS). Which could be a deal-breaker.

replies(4): >>11389592 #>>11389811 #>>11390496 #>>11390620 #
tavert ◴[] No.11389811[source]
You realize cygwin's setup.exe package manager has a CLI, right? The issue with pacman in msys2 is that it's posix dependent, which fails badly at updating the core posix layer itself. Cygwin's setup.exe is a native Windows executable and doesn't have this self hosting problem.
replies(1): >>11390000 #
koenigdavidmj ◴[] No.11390000[source]
That doesn't solve the problem that if it is trying to update the Cygwin DLL, you need to shut down everything. And if there's an update to something like bash or coreutils, same thing (since Windows does not allow writing to executables that are running).
replies(1): >>11390337 #
1. tavert ◴[] No.11390337[source]
Sure. But self-hosting pacman makes it literally impossible to do correctly. Updating cygwin itself should be done by an outside-of-cygwin solution to invoke setup.exe, just write a little powershell provisioning script or something.
replies(1): >>11390977 #
2. Macha ◴[] No.11390977[source]
?

Arch is certainly capable of updating pacman via pacman,and it's been a while but I'm pretty sure you can update apt/dpkg via the usual apt-get upgrade on Ubuntu

replies(1): >>11391493 #
3. tavert ◴[] No.11391493[source]
Those aren't operating under the restrictions imposed by Windows.