Yeah, I was about to say. The NT kernel isn’t bad at all; it’s arguably better than Linux. It’s just that an OS is more than a kernel, and pretty much all the other crap in Windows is terrible.
Honestly, what I would like them to do is make/support a modern Copy on Write filesystem so that System Restore actually works, and so that it’s easy to roll back when Windows Update borks your PC.
You don’t need Linux for either of these things. You need software engineers to build a modern filesystem or make Windows natively support ZFS or something.
It's possible during setup though I'm not sure how supported it is. Not sure why you'd really want to, writes are much slower than NTFS in general due to journaling.
For the same reason I want btrfs or ZFS on Linux; cheap snapshots so if something breaks I can easily restore to a safe point.
A large part of my complaints about Windows Update have come because it can brick your machine, System Restore doesn’t work, and so you’re stuck spending a weekend trying to back up and fix stuff.
When I ran Ubuntu with ZFS on root, I had it so that I every time apt was run, it took a snapshot. This came in handy when my WiFi driver got borked during an update; I was able to restore from a previous point, it took like ten minutes.
ReFS doesn't give you any more rollback capability than NTFS in that sense. ReFS supports file level snapshots, not volume.
And on a client machine, it's of much less importance overall (to you, it may be super important and I don't want to discount that). And on the server side, that's why we have n+2 failovers. No single machine of importance should ever be a point of failure... I realize that's not always reality but it's more or less Microsoft's position; after all, why sell one Windows Server license when you can sell 3!
I mean, I think backups and snapshots that actually work is something that most people would benefit from?
There are few pieces of software that are more universally disliked than Windows Update, and while I cannot speak for everyone the main reason I hate it so much is because it's often automatic and I've had it make my computer unbootable multiple times (and it's actually a big reason I ditched Windows completely like sixteen years ago).
If there were full filesystem snapshots and a utility to fully restore from those snapshots, I think a lot of people would be more willing to do the updates. It wouldn't be hard for users that have any tech skills at all; do what NixOS does [1] and on boot allow the user to choose an earlier snapshot to boot from if anything gets toasted.
Windows does have System Restore, but as far as I can tell that never has fixed anyone's problems at any point in time, along with the "Automatic Repair Tools" which has become a running joke in my family.
It just bothers me, because the FOSS community has solved this, a long time ago no less. Back in 2012, I used btrfs + Snapper whenever I would install a "risky" driver like a GPU or Wi-Fi chip, or whenever I did an update. When I did break my video display, restoring from the snapshot took like ten minutes, I'm able to get back into my system and fix the issue, without having to do any major surgery to the internals of Linux. I've never tried it with FreeBSD and ZFS but I suspect it's a similar process.
Microsoft is a trillion dollar corporation, they have a higher market cap than the entire GDP of NYC and Singapore combined. Why exactly can't they just augment ReFS and copy Snapper or Time Machine (with APFS)? They have infinite funds, they have access to Dave Cutler and until about a year ago Leslie Lamport, they already have a CoW filesystem and they could easily afford a license to any version of ZFS if ReFS wasn't up to the task.
[1] I know NixOS isn't doing filesystem interface, but the overall principle is the same in this instance.
NTFS getting corrupted by the tiniest errors would be one reason to use ReFS
Using it for the OS partition is not very well supported right now though (for a consumer), installing etc. works fine, but DISM doesn't support ReFS so adding features generally doesn't work
Can't recall the last time I saw a corrupt NTFS volume... even when using Storage Spaces. I'm sure it's happened to someone given Windows is in use by billions of machines, but NTFS becoming corrupt can't be all that common.
Besides, ReFS doesn't do data journaling by default.
EDIT: Just to be clear, if you don't understand when you'd use this command, do not use it. I suddenly realised people might not be familiar with formatting, and don't want to be responsible for the destruction.
Unfortunately the other crap is probably what’s going to get ported. They’ll maintain for a long while a backwards compatible version of Windows that they’ll sell for an arm and a leg, but they’ll try to move their uncaring customers to a Windows userland running on Linux.
That’s my belief, and I’m always looking for clues that it’s what develops into their long-term plan. Right now the only thing we could glean is reduced investments in Windows.
Does it really matter if NT kernel is good or not? I don't think so. What matters if it's cheaper to use Linux kernel instead of Windows kernel in terms of expenses.
Just an example. Microsoft developed several browser engines: first Trident, then EdgeHTML. Edge wasn't bad, it was on par with Chrome, may be slightly behind, but nothing that couldn't be fixed with time. But Microsoft decided to abandon it and use Blink, because that was cheaper.
I absolutely could see the same scenario in the future, when they would need to cut expenses. Just get Linux, wine, fix enough bugs to make explorer.exe and OneDrive.exe to run smoothly enough and ship it.
There is a world where Microsoft could make yet another soulless decision to kill something good they already have on the theory it would save some money, on the mistaken belief that the kernel is the problem with Windows.
One would like to believe that as far gone as they are on Windows, they’re not that far gone. But hey, anything could happen.
They don't care if Windows is good or not because they don't make any money on it. Today, the only purpose of Windows OS is to advertise (or force) other more profitable Microsoft products as cheaply as possible.
Windows & Devices is still a $14ish Billion/year or so business for Microsoft. I know that doesn’t seem like a lot, but that’s a lot of money they’re apparently not making which would make their most recent 10K filing with the SEC a lie. It’s apparently enough money they’re not making that they keep screwing with Windows in unproductive ways that make their Windows customers resent them every time they release an update.
NT is hybrid kernel, it has microkernel features, particularly with drivers if I understand correctly.
But that said, I didn't say either were "good", I said that NT is "arguably better".
ETA: I reread my comment; you're right, I actually said that NT "isn't bad at all". I stand by what I said mostly though; that doesn't imply it's "good" necessarily, just that it's arguably better than Linux.
NT is a monolithic kernel and "hybrid kernel" is a pure marketing term. You can move functionality out of the kernel into userspace or not. There is no in-between.
I also don't get why people claim NT is "better." Linux is a modern kernel under very active development.
The graphic stack in NT is done in a microkernel fashion, it runs in kernel space but doesn't (generally) crash the whole OS in case of bugs.
There are a few interviews of Dave Cutler (NT's architect) around where he explains this far better than I am here.
Overall, you have classic needs and if you don't care about OSS (either for auditability, for customizability or for philosophical choice about open source), it's a workable option with its strength and weaknesses, just like the Linux kernel.
Parts of the kernel can be made more resilient against failures, but that won't make it a microkernel. It'll still run in a shared address space without hardware isolation. It's just not possible to get the benefits of microkernels without actually making it one.
Also Linux being OSS can't be dismissed because it means it'll have features that Microsoft isn't interested in for Windows.
Modern Linux supports asynchronous I/O. It's debatable whether NT's lack of memory overcommitting is a superior choice. OS personalities have never been relevant outside of marketing and might even be technical debt at this point, as virtualization offers a more effective solution with significantly less complexity. Moreover, the Linux kernel maintains a stable ABI.
Much of the discussion surrounding NT's supposed superiority is outdated or superficial at best. Linux, on the other hand, offers several advantages that actually matters. It supports a wider variety of filesystems natively, with FUSE providing exceptional utility. Linux also accommodates more architectures and allows for more creative applications through features like User Mode Linux and the Linux Kernel Library. It also has a more robust debugging ecosystem thanks to its large community and open source nature. All of these things are possible because Linux isn't bound by a single company's commercial interests.
Also, is Microsoft putting as much effort into NT these days? I find it hard to believe they care about NT when they stopped caring about what runs on top of it, leading to articles like this one.
Not nearly to the depth and breth of NT. NT is async I/O throughout. Linux has a bunch of libs that ride on top of pretend async I/O with io_uring as a more recent bonus.
> It's debatable whether NT's lack of memory overcommitting is a superior choice.
NT won't randomly kill a process. That's the winning play.
> OS personalities have never been relevant outside of marketing
Until you've used them for non-marketing purposes, then they're invaluable. Personalities existed when virtualization didn't exist on x86.
> Moreover, the Linux kernel maintains a stable ABI.
The only stable ABI on Linux is Win32.
> It supports a wider variety of filesystems natively,
Most distros suggest ext4 out of the box. Sysadmins are going to deploy ZFS where it counts. Some might use XFS. Having access to a ton of file systems is great, but the usage outside of ext4 is going to be comparatively low. ext4 is the only FS I'd want to see as first-party on Windows as a data drive. But that would have been more important before persuasive networking.
> It also has a more robust debugging ecosystem thanks to its large community and open source nature.
This ignores the debugging tools on Win32 by a country mile.
> is Microsoft putting as much effort into NT these days
Yes. Even if you do the bare minimum investigative effort and follow the "what's new" for each version of Windows, you can see the kernel-level investment. Much of this is around security and isolation of kernel components. There is also Microsoft in talks (finally, again) with EDR vendors to isolate their solutions; hopefully game devs are next.
> leading to articles like this one.
This isn't an article. It's an uninformed blog post.
> Not nearly to the depth and breth of NT. NT is async I/O throughout. Linux has a bunch of libs that ride on top of pretend async I/O with io_uring as a more recent bonus.
Is this a purity thing or does it have practical implications?
> NT won't randomly kill a process. That's the winning play.
Every OS will have to when it runs out of resources. No overcommitting means it's less resource-efficient too, so things aren't that simple.
> Until you've used them for non-marketing purposes, then they're invaluable. Personalities existed when virtualization didn't exist on x86.
When have OS personalities ever been a commercial success? Every product that built on it went nowhere.
> The only stable ABI on Linux is Win32.
Containers and Flatpaks prove otherwise. Static binaries exist, too.
Also, if you're extending this Linux / Windows comparison to include the userland, then Windows is no match for Linux. Not when Microsoft is actively sabotaging Windows.
> Having access to a ton of file systems is great, but the usage outside of ext4 is going to be comparatively low.
What on earth? There's more use to filesystems than mounting it at root. Are you really claiming that OS personalities are useful, but being able to mount any filesystem is not? That's absurd.
Which doesn't mean much without an ecosystem of programs using WinFsp that's comparable to Linux. Moreover, the long-term development of WinFsp isn't guaranteed, and there remains the risk that Microsoft could introduce changes that might impede the functionality of third-party filesystems.
> It's an uninformed blog post.
Uninformed? While an official Windows-themed Linux distro doesn't make sense, the observation that Windows is declining and Microsoft no longer cares at all what users think is very much correct and obvious to anyone. The fact that Microsoft hasn't ceased development doesn't negate this fact.
> Every OS will have to when it runs out of resources. No overcommitting means it's less resource-efficient too, so things aren't that simple.
NT does memory overcommit...
> When have OS personalities ever been a commercial success? Every product that built on it went nowhere.
Xceed made money off of it. Yes, every product has a shelf life. Just like every commercial Unix. They were successful at what they did until a replacement came along.
> Also, if you're extending this Linux / Windows comparison to include the userland, then Windows is no match for Linux. Not when Microsoft is actively sabotaging Windows.
You're not saying anything, here. "No match" how, exactly?
> There's more use to filesystems than mounting it at root. Are you really claiming that OS personalities are useful, but being able to mount any filesystem is not? That's absurd.
Absurd, how? Is mounting HFS /really/ that critical to your day-to-day?
> Which doesn't mean much without an ecosystem of programs using WinFsp that's comparable to Linux.
Movin' those goal posts!
> Uninformed? While an official Windows-themed Linux distro doesn't make sense,
You uh... did read the post, right? That's what the entire thing was about!
Actual lightweight isolated processes? The docs are pretty vague about what the windows containers are and they still indicate that both Hyper-V and a chosen kernel is used - so that smells like a VM. Also, available only in windows 10 pro and higher, so no w10 in general.
Yes, there are two modes, Hyper-V isolation and process isolation, which is similar to how Linux does it.
The kernel version has to do with process isolation not being fully there when Windows containers were initially supported, so they had the limitation the container kernel dependency had to match the host version.
Since Windows 11 this has been relaxed.
The namespacing approach is based on Jobs API.
Modern Windows security relies on several sandboxed components, Hyper-V is always running anyway, also one of the reasons of the updated harware requirements, while this configuration is optional on Windows 10, it is always enabled on Windows 11.
Honestly, what I would like them to do is make/support a modern Copy on Write filesystem so that System Restore actually works, and so that it’s easy to roll back when Windows Update borks your PC.
You don’t need Linux for either of these things. You need software engineers to build a modern filesystem or make Windows natively support ZFS or something.