{"id":25219,"date":"2019-05-10T15:43:06","date_gmt":"2019-05-10T19:43:06","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=25219"},"modified":"2019-05-13T14:26:08","modified_gmt":"2019-05-13T18:26:08","slug":"windows-to-include-a-full-linux-kernel","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/05\/10\/windows-to-include-a-full-linux-kernel\/","title":{"rendered":"Windows to Include a Full Linux Kernel"},"content":{"rendered":"

Microsoft<\/a> (via Miguel de Icaza<\/a>):<\/p>\n

\n

We will be shipping a real Linux kernel with Windows that will make full system call compatibility possible. This isn’t the first time Microsoft has shipped a Linux kernel, as we have already shipped one in 2018 when we announced Azure Sphere. However, this will be the first time a Linux kernel is shipped with Windows, which is a true testament to how much Microsoft loves Linux! We’ll be building the kernel in house from the latest stable branch, based on the source available at kernel.org.<\/p>\n

[…]<\/p>\n

WSL 2 uses the latest and greatest in virtualization technology to run its Linux kernel inside of a lightweight utility virtual machine (VM). However, WSL 2 will NOT be a traditional VM experience. When you think of a VM, you probably think of something that is slow to boot up, exists in a very isolated environment, consumes lots of computer resources and requires your time to manage it. WSL 2 does not have these attributes. It will still give the remarkable benefits of WSL 1: High levels of integration between Windows and Linux, extremely fast boot times, small resource footprint, and best of all will require no VM configuration or management.<\/p>\n<\/blockquote>\n\n

What a time to be alive. Does this mean that Microsoft will now ship more up-to-date Unix tools<\/a> than Apple?<\/p>\n\n

Owen Williams<\/a>:<\/p>\n

\n

Including a Linux kernel in Windows changes the game. Instead of a Linux environment that has barriers and known edge cases, this is a full-on, no-limitation, macOS-esque Linux environment—with a notable improvement: it’s containerized so you can dispose of it and get a fresh environment in a second, then just keep working.<\/p>\n

[…]<\/p>\n

The master stroke here is that including a Linux kernel in Windows also <\/em>dramatically changes the cloud story for Microsoft. Windows Server just gained a huge leg up, now able to run Linux and Windows tooling side-by-side on the same system, making developer tooling and deployment of code significantly easier.<\/p>\n

[…]<\/p>\n

By building the absolute best developer experience—from acquiring GitHub, to creating the most popular coding tool VSCode, and now, a fully-functioning Linux environment, Microsoft can say it provides the best tools for developers, period, wherever they are.<\/p>\n<\/blockquote>\n\n\n

Tom Warren<\/a>:<\/p>\n

Microsoft also announced Windows Terminal<\/a> today, a new command line app for Windows. It’s designed to be the central location for access to environments like PowerShell, Cmd, and the Windows Subsystem for Linux (WSL).<\/p><\/blockquote>\n\n

Casey Liss<\/a>:<\/p>\n

\n

Everyone doing web development switched to using then-OS X back in the aughts because we could run the entire stack locally, natively. And the keyboards worked.<\/p>\n

Seems like soon you’ll be able to do the same on Windows. Where the keyboards work.<\/p>\n

🧐<\/p>\n<\/blockquote>\n\n

Paul Haddad<\/a>:<\/p>\n

\n

MSFT has two different ways of running Linux binaries on a Windows machine but 32 bit Mac binaries are just too much work for Apple.<\/p>\n<\/blockquote>\n\n

Alex Stamos<\/a>:<\/p>\n

\n

This is smart and well-timed. Windows is becoming a legitimate competitor to OS X for cloud-native development at a moment when Macbook Pro users are screaming for working keyboards and features like LTE.<\/p>\n<\/blockquote>\n\n

Stephen Nellis<\/a>:<\/p>\n

\n

I can envision developers on their 3rd trip to the overrun Union Square SF Apple store to get a MBP keyboard fixed, thinking...well, maybe it”s time to take a look?<\/p>\n<\/blockquote>\n\n

Peter Steinberger<\/a>:<\/p>\n

\n

I admire the new Microsoft. Not only are they super transparent about their plans, release everything open source - they also share Twitter handles of the main folks responsible.<\/p>\n<\/blockquote>\n\n

Damien Petrilli<\/a>:<\/p>\n

\n

Microsoft is making great progress at attacking macos exactly where it hurts: development.<\/p>\n

We are really not far from seeing how Tim Apple miss management is going to kill a lot of Apple’s value for good.<\/p>\n<\/blockquote>\n\n

Doug Gregor<\/a>:<\/p>\n

\n

People are excited about a terminal. Either the 90’s are back or it’s a really slow news day in the tech world<\/p>\n<\/blockquote>\n\n

Damien Petrilli<\/a>:<\/p>\n

\n

Nope, it just means that now, there is a real competition to macos on the dev side.<\/p>\n

A lot of people including myself are on macos because of its UNIX subsystem. It’s the best platform for all open source \/ programming language.<\/p>\n

This could change soon.<\/p>\n<\/blockquote>\n\n

Marco Arment<\/a>:<\/p>\n

\n

If you’ve wondered why Microsoft made the VS Code editor, note how many lines go from “First” to “OSX” [sic] to “Visual Studio Code”.<\/p>\n

Macs OWNED web development for a decade. But when Apple lost years alienating and neglecting pros, Microsoft had their foot on the gas.<\/p>\n<\/blockquote>\n\n

Alex Harden<\/a>:<\/p>\n

\n

VS Code is not my primary editor (@AtomEditor is) but I may end up using it more if\/when I end up on Windows 10 this fall on my work computer. I simply can’t justify staying on MacOS for work when @Apple isn’t designing MacBooks for developers any longer.<\/p>\n<\/blockquote>\n\n

Marco Arment<\/a>:<\/p>\n

\n

This perspective (a common one) should be most worrisome to Apple:<\/p>\n

“The MacBook Pro seems designed for other people’s needs, not mine.”<\/p>\n

…especially coming from developers, which Apple has said are their largest category of “pro” users.<\/p>\n<\/blockquote>\n\n

Anonymous Genius<\/a>:<\/p>\n

\n

The irony is that Apple messed up the Mac Pro and the MacBooks Pro by solving problems that didn’t need to be solved. They didn’t neglect them: they over-designed them, fixed what wasn’t broken, and then didn’t fix the keyboards when they broke.<\/p>\n<\/blockquote>\n\n

Justin Flood<\/a>:<\/p>\n

\n

I’m a pro photographer. I don’t feel like the MacBook Pro is made for me anymore. I work with video editors and VFX people, and musicians who feel the same. This asks the question:<\/p>\n

Who IS the MacBook Pro designed for?<\/p>\n<\/blockquote>\n\n

Ken Kocienda<\/a>:<\/p>\n

\n

The success of the iPhone, iPad, and Apple Watch relieves much of the burden from Macs to be the “computer for the rest of us”. It means the Mac can stress power and flexibility as a platform for pros, a tool for developers, and a playground for hobbyists.<\/p>\n

After all, pros, developers, and hobbysists are the people that feed the iOS ecosystem with content, apps, and new ideas. Mac and iOS devices already support each other in a virtuous cycle, but that could be stressed more by producing machines that pros and geeks truly love.<\/p>\n

I sure hope Apple soon gets through this period of problematic hardware (MacBook keyboards), “Where is it?” hardware (Mac Pro), and of new languages and frameworks that do mostly what the old ones did, only differently (Swift, Marzipan). Bring back “Insanely Great”!<\/p>\n<\/blockquote>\n\n

Ken Kocienda<\/a>:<\/p>\n

\n

The reliability and usability failings of the MacBook Pro are rooted in thinness and weight-saving—yet Apple makes the MacBook Air to optimize for those design goals. Let’s face it. Apple doesn’t make a pro laptop today. Sticking “Pro” on the end of the name does not make it so.<\/p>\n<\/blockquote>\n\n

Petter Ahrnstedt<\/a>:<\/p>\n

\n

Ex Apple employee here (PR manager). They stopped caring about prosumers in 2011-12. The prosumer managers were made redundant. Entire focus is (was) on consumers.<\/p>\n<\/blockquote>\n\n

See also: The Talk Show<\/a>, Hacker<\/a> News<\/a> (3<\/a>).<\/p>\n\n

Previously:<\/p>\n