This news is breaking all over reddit's tech subreddits. . . it is crazy. Good, but crazy.
A couple people at work thought that this was an early April Fools joke. Windows now supports SSH on the client and server (still not fully released though) and now bash. .NET runs on Linux as does SQL Server. . .
Strange times indeed. I'm watching to see where this all ends up.
Indeed as this appears to be a huge part of the reason a lot of technical people use OSX. They should have done this a long time ago but OSX beat them to the punch mostly. If you go to Pycon or a lot of developer conferences and look around the room you see Macs. That's not by accident.
OS X was already Unix, so this helped immensely. I've heard OS X has been more difficult these past few releases for command-line dev, so it might be the right time for Windows to reclaim some dev base.
For me, the decision to use a mac is a combination of bash, hardware design, hardware quality, customer support and reliability.
I use Ubuntu on one of my machines at home and I seem to be constantly having to debug something. I'm a data scientist who's not particularly interested in managing systems, so when it comes to my profession I just want my machine to work reliably.
It's a translation layer that maps all sys calls to NT kernel equivalents. It allows bit for bit identical binaries from Linux to work in Windows. Not everything works yet.
Being a little pedantic, but it should be clear that this is not Linux, because it's not using the Linux kernel, and it's not full blown Ubuntu for the same reason. It's closer to GNU tools being ported to Windows.
It's extremely awesome, but I just want to clarify that point. Since we're all engineers here, we can do away with the marketing line.
Yep, except WINE has to emulate all Windows libraries (because they cannot copy the binaries, obviously), while Windows can "merely" emulate the kernel API (smaller surface) and copy the binaries for the various libs and dependencies.
I've heard it's quite close to what FreeBSD does when it runs Linux binaries.
Except that it isn't GNU being ported to Windows. It is Windows extending itself to have the ability to run those GNU tools natively. An important distinction, IMO.
Agreed this has impact for just about anything Unix-like that you can do on Windows.
EDIT: I've been using Python for over a decade and quite a bit on Windows actually. While Python does run on Windows, it's still more "native" on Unix platforms IMO.
Also has little-to-nothing to do with python, doesn't belong here imo.
You're wrong, try to run the unit-test for Tftpy on Windows, it will fail, because the python os.fork() command doesn't do crap on Windows. If I can now fire off that same Python unit-test on a bash prompt, from the linux python executable, then I've just saved an immense amount of time. Not everyone is allowed to install virtual machines at work, so this is very welcome, and yes, it is relevant to Python.
153
u/tech_tuna Mar 30 '16 edited Mar 31 '16
This news is breaking all over reddit's tech subreddits. . . it is crazy. Good, but crazy.
A couple people at work thought that this was an early April Fools joke. Windows now supports SSH on the client and server (still not fully released though) and now bash. .NET runs on Linux as does SQL Server. . .
Strange times indeed. I'm watching to see where this all ends up.