81–90 of 142 posts
The damned terminal kept making characters disappear! I actually thought my interviewer was inadvertently deleting characters, or maybe trolling me.
I had to switch to using an actual Linux system.
MS have a ways to go before getting this right. I daresay I'll be on OSX by the time that happens though.
I'd just like to interject for moment. What you're refering to as WSL, is in fact, GNU/NT, or as I've recently taken to calling it, GNU plus NT. NT is not an operating system unto itself, but rather a non-free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX. Many computer users run a modified version of t…
If MS had actually ported the GNU base system to NT, then you could reasonably call it GNU/NT. They have not done that.
I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
Whatever name is better than "Bash for Windows", the worst possible name and the least tech-savvy way of describing what is going on. A real embarrassment. They justify their choice saying they had a survey where the most popular option was Bash for Windows. Well, surveys also led to a boat called Boaty McBoatface...
I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
It's a subsystem of Windows (hence Windows Subsystem). And, among all Windows Subsystems, it's the one for Linux, hence Windows Subsystem for Linux.
I gave up WSL after experiencing significant performance drop on GHC, Stackage. It was less than 1/10th of native for compiling Haskell code.
I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
Edit: seriously, I'm just kidding
I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
Earlier quoted context omitted.
That's a bit loaded, but I'll attempt to answer seriously: Can you replace Ubuntu? Maybe, if you are OK with 14.04 LTS level support. Certain simple things straight up don't work -- you can't send a ping without an admin level windows shell (sudo wont do it either). You also won't magically get driver support for hardware that works in Linux, but not Windows (if you think this isn't a thing, try plugging in a random…
> That's a bit loaded, but I'll attempt to answer seriously: Fair enough. I specifically mean, can I replace Ubuntu for development work? Can I use apt-get to install various tools? Does docker work better? That sort of stuff.
http://serverfault.com/questions/767994/can-you-run-docker-n... has a good set of answers.
I'd just like to interject for moment. What you're refering to as WSL, is in fact, GNU/NT, or as I've recently taken to calling it, GNU plus NT. NT is not an operating system unto itself, but rather a non-free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX. Many computer users run a modified version of t…
The interesting bit of WSL (what the article talks about) is a Linux syscall translation/emulation layer, as well as ELF64 binary support (not specific to Linux, but not specific to GNU either). You can certainly install the Linux versions/ports of GNU tools and run them under WSL, and that's what the stock setup looks like, but an important component of WSL is about emulating a Linux (the kernel) environment. If MS…
What's the use of Linux syscall -> NT syscall translation if not compatibility with developer tools, most of which are GNU software?