←back to thread

535 points raddad | 1 comments | | HN request time: 0.206s | source
Show context
quotemstr ◴[] No.11391643[source]
Oh, another subsystem. Yay, good for Microsoft. The problem with the subsystem approach is that it's hard to get programs running in the subsystem to interact with the desktop world, which is win32. What I like about Cygwin is that the programs that run under it are win32 programs: they can equally well use CreateWindow and ppoll. Cygwin programs understand NT permissions.

It's always been possible to run Linux programs under Windows: just run a VM. What Microsoft has done here makes it less painful to run Linux programs, sure, but these programs still exist in their own little world. Cygwin programs, on the other hand, are Windows programs. To me, that makes them much more useful.

Now, maybe I'm wrong. Maybe the new Linux subsystem is more tightly integrated with the rest of the system than I'm guessing. But based on the available documentation, it looks a lot more like SFU or Interix than it does Cygwin, and that's a shame, because if I'm right, Microsoft misunderstood the whole point of Cygwin. Again.

replies(2): >>11391790 #>>11418190 #
1. JdeBP ◴[] No.11418190[source]
> Cygwin programs understand NT permissions.

Windows NT POSIX subsystem programs understand NT permissions, too. There's quite a lot about it in the Interix doco, explaining how ACEs are mapped and so forth. This is not a problem with the subsystem approach, demonstrably.