The biggest problem with Cygwin is that programs linked with Cygwin inherit global state from from a Cygwin installation on the system th...

The biggest problem with Cygwin is that programs linked with Cygwin inherit global state from from a Cygwin installation on the system they're running on. If you want to produce a Windows program that just runs on any system you install it on using Cygwin, it will work right for most users, but if a power user who has Cygwin installed and has their own custom mounts, options (like different binary/text mode settings), etc. tries to run your program, it might break spectacularly. This makes Cygwin a really poor choice for making binaries you want to distribute as standalone programs. Aside from that, Cygwin tries to hard to be a complete Unix environment on Windows, whereas midipix just gives you enough to use interfaces that were standardized in POSIX as a reasonable, uniform API for all operating systems to provide. Some functions go beyond that, but you don't have to use them. And even some things that are mandatory in POSIX are optional in midipix; as I understand it, you can choose at build time whether you want the overhead of being able to support tty devices (and the associated semantics like job control, signals from the controlling tty, etc.).

Posted by dalias on Jun 3, 2015, 6:19 PM

Tags

• ux (Other)

Related issues

• To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
• > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
• Custom trigger IDs are not displayed in the new 2026.10 trigger selector
• I hate that too, but I think it’s more the ux than the concept of a default.
• > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
• "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.