Agree, NT has many excellent ideas. But re-implementing it today seems silly. Are you going to have messages with take two integers only, then stick two 16-bit

Agree, NT has many excellent ideas. But re-implementing it today seems silly. Are you going to have messages with take two integers only, then stick two 16-bit fields into second one? Look at these articles, do you think anyone should be implementing API like this in 21st century: https://blogs.msdn.microsoft.com/oldnewthing/20070710-00/?p=26083 https://blogs.msdn.microsoft.com/oldnewthing/20070710-00/?p=... https://blogs.msdn.microsoft.com/oldnewthing/20120913-00/?p=6613 https://blogs.msdn.microsoft.com/oldnewthing/20120913-00/?p=... I am all for variety. Hurd, L4 -- these are fundamentally different from Unix and very interesting. ReactOS? well if you enjoy debugging windows kernel drivers without source code...