News for hackers. Stuff that matters.
Re:Microsoft blames monster email outage on software defect ... by mike_hearn on Tuesday November 17, 2026 @05:21AM (#50529616)
It's not that great. The idea it's amazing is a bit of a meme. There are many things about the Windows kernel that are much worse than Linux.

Consider: exclusive file locking for almost everything. UNIX lets you delete or move an open file, the Windows kernel doesn't and this creates enormous complexity at higher levels of the userspace stack especially for any kind of auto updater. It's also one reason Windows updates are so painful.

Windows has pathetically low performance in the filesystem layer, largely thanks to its filter driver design. It's not uncommon to find apps written originally for Linux are basically un-portable to Windows because they assume fast file IO and Windows just can't provide it. This was also a major motivator of the WSL2 effort. Windows actually has a feature called Dev Drive. It's a whole alternative filesystem that's faster than NTFS. They call it Dev Drive because they assume only devs need good filesystem performance (gah). You can't run Windows itself on a Dev Drive though, because of tech debt-y "reasons".

This ridiculous approach of assuming developers are special is carried over to other things too. Windows supports symlinks but this support is nearly useless, because it's disabled out of the box for security reasons (symlinks play a role in some kinds of attack on Linux). So you have to turn on Developer Mode in the control panel to be able to use them.

Sometimes you'll see the Windows approach to security be praised (SIDs, object manager etc). It does have a more principled design than Linux, that's true, but the standard here is macOS/XNU not Linux and the Windows kernel's sandboxing support is far worse than macOS.

Windows processes are extraordinarily heavy compared to a Linux process. They take more RAM, start up much slower, and context switching is slower. Again, this difference often renders Linux software un-portable because they assume they can fork and exit processes very fast, but on Windows you just can't. You pretty much have to replace a multi-process design with threads.

Despite the Windows kernel not being a competitive advantage to Microsoft (IMHO), and despite that they run public symbol servers, they keep it closed source. If you really want to understand the Windows kernel you can do so down to the level of individual function calls with public information, but you can't actually read them. The reason is probably security-through-obscurity for DRM, Warbird and other such things, not that it seems to help much. This makes it frustrating to figure out what's going on.

Relatedly, the Windows kernel is an absolute war zone. It's nothing like Linux, which is a conventional textbook OS design. On Windows the kernel is riddled with deliberate traps, code obfuscation engines and "tilt sensors" designed to try and block attempts to hook internal functions by malware or other kinds of malicious software. This shows up in other places too: for example, the API to Linux is the system call instruction. On Windows the kernel theoretically doesn't have a stable syscall interface and you're supposed to go via public APIs like kernel32.dll, which in turn just forwards to ntdll. In practice it does have stable syscalls because MS never randomized the system call interface, so apps trying to detect hooking in userspace do invoke system calls directly (often for anti-cheat purposes). The result is there are like three different ways to invoke NT system calls, all of which are extremely overlapping and duplicative (kernel32, ntdll, system calls), all of which are used by apps in reality but only one of which is documented.

Re:Microsoft blames monster email outage on software defect ... by torginus on Tuesday November 17, 2026 @07:24AM (#50530462)
I would contest your contestation. While I admit that Windows suffers from lack of engineering attention as of late compared to Linux, but many of these things

- File locking is a convention on Windows, not a necessity and you don't pay for it if you don't lock files (which is an unfortunate default btw).

- By filter drivers being slow, I think you mean antivirus and security stuff, which are an unfortunate reality of daily windows use, but aren't really caused by filter drivers being a thing. If you needed antivirus on Linux, I think you might incur a similar penalty

- I think symlinks would be nice, but I haven't ever really missed them on Windows. The things linux uses it for, like linking libraries are done differently on Windows

- Devs are special in some sense. You can't afford to break existing workflows on users machines. Just recently, the EU decided to replace Windows with Linux, discovered that stuff doesn't work, then promptly went back

- I appreciate that you call out Windows security as a positive, but as with many other subsystems, Windows has shipped with many systems that were production grade and built in, like security, ACLs, event logs, etc. etc. which are not part of Linux by default, and are the subject of endless debates as to how to implement them (some of them, like systemd, mirror Windows functionality)

- A concept of a Windows process doesn't really map to a Linux process. Linux processes are isolated threads, while Windows ones are containers (and don't even necessarily have a main thread). And afaik Windows processes aren't that heavy any more. Their heaviness came from loading gdi32 and user32 dll, as they expected to host GUI apps, on new Win versions, that's no longer necessary. But fork() style process management is foreign to Windows, and the one place where its useful in Linux, cli apps, Powershell has an entirely different design, where its more like a JITed scripting language, and ls or cp are not separate processes.

- I don't think heavily multiprocess designs are in vogue anyways (at least not how Linux does them), but in terms of RPC, COM multi-process RPC was much more efficient in Windows compared to things like eventfd. Android even added binder, which is a similar mechanism

Many of Windows' mechanisms are a bit long in the tooth, but arguing that Linux is better, then adopting a very similar mechanism in Linux years to decades later doesn't really show that engineering superiority.

I'm not a Linux hater btw, except in one thing - the fact that there's no good standard way to build and distribute binaries that can be expected to work on any reasonable Linux install is criminal.

Re:Microsoft blames monster email outage on software defect ... by mike_hearn on Tuesday November 17, 2026 @10:27AM (#50532680)
A few unimportant quibbles... you can't avoid locking files on Windows because the OS locks EXEs and DLLs automatically.

IIRC it's more that the filter architecture itself is slow, but yeah Windows comes with some slow filters out of the box that don't help. There's a writeup somewhere about this from a Windows kernel engineer but it was years since I read it. AV is indeed the worst offender but Windows always has one, so <shrug>.

systemd is inspired by macOS Launch Services. I guess svchost is the closest equivalent in Windows, but it didn't play any role in the systemd design process.

Linux processes do contain threads, I didn't quite understand what you meant by saying they're not containers. There is now the concept of a Windows picoprocess but it can't do much and isn't used after WSL1 was removed, if I understand correctly. I agree that Windows doesn't really need cheap processes architecturally and native apps don't rely on them without that imposing much cost.

[D]COM isn't a kernel feature but the closest equivalent on Linux would be DBUS, not eventfd. I don't know how they compare in terms of efficiency, I'd expect about the same, although in a past life I actually worked on an open source implementation of DCOM!

I didn't argue Linux is better, I have plenty of beefs with how Linux works too :) The Windows kernel is rightly very popular because it offers a stable driver API, which in turn enabled a huge gaming and hardware ecosystem, for instance. But architecturally I don't see big differences between them tbh.

Now Midori, on the other hand... that really was different!

Re:Microsoft blames monster email outage on software defect ... by cowlevel on Tuesday November 17, 2026 @08:33AM (#50531132)
A lot of this cuts both ways. Linux not locking files creates as many problems as it solves, as do hard links.

I see that in general Windows takes a "big monolith" approach to things that Linux can handle as a large array of small pieces. An app can be a few files on Windows, a help database is one file, a source code repository would be one file if all the VCSes weren't imports from Linux.

This might be Conway's law in action. On Windows you were more likely a proprietary shop writing software that just does what it should do - if you needed to change it then you changed the software. On Linux because it's a bazaar you have a lot more of trying to tinker with the things that are already there, or add on small pieces. The average unit of deployment on Microsoft platforms is (or was) Turbo Pascal or Visual C++ 6 or QuickBooks or Microsoft Office; the unit of deployment on open-source platforms is grep or sed.