News for hackers. Stuff that matters.
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!

There are no comments on this comment yet.