4 ms·
> But I don't think there's any reason to invoke EEE! until they have introduced a proprietary (i.e. closed-source) implementation of something and then added n
by lokedhs 7y ago
> But I don't think there's any reason to invoke EEE! until they have introduced a proprietary (i.e. closed-source) implementation of something and then added non-standard extensions.
That would be WSL wouldn't it? Their goal is clearly to avoid having people moving to Linux as a development platform, and keep them on Windows.
The extensions are the ability for Linux processes to integrate with Windows software running on the same machine. In a way, they're extending Linux with Windows services.
- carlosdp 7y ago> Their goal is clearly to avoid having people moving to Linux as a development platform, and keep them on Windows. I think it's the opposite. There's little danger that Windows shops are going to move to Linux. However, I know a bunch of devs currently using Macs that would probably switch to Windows with nice devices like the Surface Pro and access to real gaming and such, if only Windows was a suitable Unix environment for their work. They want devs using Macs and such to move to Windows, and I think it's going to work.
- acct1771 7y agoThis comment tells me Purism et al need tablets next.
- TimTheTinker 7y agoThe only implementation built by Microsoft of any standard in WSL is the bridge that provides a Linux kernel interface (it proxies Linux syscalls to the NT kernel). But their only goal there is to support Linux userspace, so it would be rather pointless to add extra syscalls or extend the existing ones. (And besides, they haven't even finished implementing all of the system calls...) For WSL 2, they're taking the Linux kernel whosesale and dropping it into a VM in Hyper-V. If anything, they're backing away from anything that could be construed as a possible EEE.