Windows 10 is getting a Microsoft-built Linux kernel (opens in new tab)

> MS embracing CLI.. feels out of place

Not so much to those of us old enough to remember when the two main personal computing platforms were DOS and MacOS.

> And I always used to wonder why they were so crazy about their Apple laptops when all they were using was the terminal. Why couldn't they install Linux on way more powerful hardware at a fraction of the cost.

It's less about the power of the hardware, and more about support. A top end 13" Macbook Pro is $2000 for an i7, 8GB RAM, 512GB SSD a passable integrated GPU and 2280x1800 resolution.

A Dell xps 13 "developer edition" comes to just shy of $1700 with very very similar specs and a similar build quality, which is the same ballpark. People aren't buying macbooks because they're expensive, they're buying them because the hardware support is (well, was) good, the software is good, they work together, and there's a fallback.

Install any linux distro on a HP laptop for a third of the price, and see how far you get in terms of support.

> And I always used to wonder why they were so crazy about their Apple laptops when all they were using was the terminal.

But it was a nice terminal! On a more serious note: The cost of purchasing an Apple laptop is dwarfed by the cost of selecting a set of hardware that works with Linux. I did switch from Apple to Linux in one of the last iterations and despite using a Thinkpad, the time I sink into making sure that my machine works, does a proper backup that I can restore, ... is higher than the one-time price difference to a nice Apple laptop. Their hardware is good for years, it’s usually working pretty well. It comes with a price tag, true, but so does maintenance for a Linux machine.

I have disabled antialiasing altogether on my computer (which sadly now can only be done via the registry, WTF Microsoft?) but several applications (thankfully it is mostly UWP crap, but it is also stuff like IE and the IE ActiveX control, which includes CHM files) ignore that setting (and often ignore ClearType too so even if you have ClearType set up, they do not use subpixel antialiasing).

Only a third party application called MacType was able to get Linux/MacOS quality font rendering. Since Windows 10 MacType no longer works as Microsoft changed the underlying font rendering API.

My issue is across the whole windows platform not just WSL. If you check large repos out on windows native it sucks too. Rather than just fixing WSL and declaring victory they should fix the NTFS problem.