News for hackers. Stuff that matters.
Re:GNU/kWindows by dikaiosune on Friday April 08, 2016 @06:33PM (#11458623)
But it's not just GNU running on top of the Windows kernel. It's GNU executables which think they're communicating with a Linux kernel. I understand being frustrated about the already-forming naming conventions (although they've been chanting GNU/Linux forever and it still isn't used in common parlance), but GNU/kWindows doesn't capture the nature of the system either.
Re:GNU/kWindows by ecma on Friday April 08, 2016 @06:47PM (#11458706)
Accurate. Technically the Microsoft compatibility later could have been entirely done at the library level by replicating POSIX and adding an ELF linker/loader. There would have been some edge cases around Linux specific source but the GNU core would have been well served by something like that.

The reason the language is all centered around Linux is because what they chose to do was do a Linux syscall compatibility layer. Really it could be called GNU/sLinux/kWindows but nobody is ever going to bother with that mouthful.

Edit: I should add that this doesn't mean I agree with the use of Linux here - I just understand why that's the case. I would much prefer if those involved went to the trouble of explaining what GNU is to those consumers who are interested. Pretty unlikely Microsoft would be leading that given GNU's position on Windows.

Re:GNU/kWindows by ryao on Friday April 08, 2016 @08:13PM (#11459152)
Cygwin does that. forking does not perform very well.
Re:GNU/kWindows by anonymfus on Friday April 08, 2016 @06:43PM (#11458689)
GNU/WSL