Edit: lol, yep. http://www.nextcomputers.org/NeXTfiles/Docs/Developer/Driver...
You'd think they wouldn't name it something that literally conflicts their previous deprecated framework.
Obviously no technical recycling going on though; the new DriverKit allows user-mode drivers, not ObjC in the kernel or willy-nilly patching of the OS.
Like, the XNU kernel has now had three driver frameworks. Two of them are named DriverKit but are completely separate, and not even back to back.
Edit: you might have an argument on the WSL-WSL2 transition. But, IMO, that feels more like a exokernel than a microkernel since it's running on the side over Hyper-V.
Edit: and the GPU drivers still very much have a kernel component, and more or less have to. The creation of a GPU instance is super duper privileged, since it's setting up page tables. If you allowed user space to do that, you'd be able to circumvent the MMU.
Same applies to USB drivers not doing a kernel panic when plugged on.
Naturally there is always a part that only the kernel is allowed to own control over.
None of that has to do with the kernel/user boundary. It's that dwm does a better job recovering than x11. Wayland also does a better job recovering.
> Same applies to USB drivers not doing a kernel panic when plugged on.
Like I said, Linux has had USB drivers in user space for longer than NT, and I've def recently had NT USB drivers bluescreen my system.
> Naturally there is always a part that only the kernel is allowed to own control over.
I mean, not necessarily. I've seen true ukernels run GPU drivers entirely in user space. It's just that NT isn't at all a ukernel. They just like to call it a hybrid because the executive is a different folder in their source code, lol.