bash - Differences between MSYS2 and Cygwin -
traditionally msys bash has been considered inferior cygwin bash. former ancillary tool inside mingw intended running autoconf scripts. there mingw-w64 , msys2. latter ships sweet pacman package manager , elegant shells zsh, wonder if there still gap in emulation layer.
while mingw* applications windows native executables, msys2 software requires posix-emulation layer, cygwin does. @ least casual user, hard spot differences between two.
- which functional differences between 2 emulation layers (if any)?
- which emulation faster (more efficient)?
traditionally msys bash has been inferior, because cygwin remained under active development whereas msys didn't. msys forked cygwin version 1.3.3 , never re-synced, whereas msys2 resyncs cygwin project regularly.
we don't have "sweet pacman package manager", have direct re-compilation of arch linux's pacman package manager achieve.
msys2 doesn't have cygwin.dll have msys-2.0.dll same thing (and more besides). specifically, arguments paths , path env. var converted windows form when running windows-native software.
as whether it's slower, expect there'd little difference msys2 tiny amount slower due conversion work. again, chances you'll run more windows-native software within msys2 (such mingw-w64 compilers) cygwin that'll shift things in msys2's favour.
Comments
Post a Comment