vMotion is a sort of crude version of VMS live process migration between nodes.
The security model is very well thought out, beats rwxrwxrwx and setuid hands down. Versioning filesystem, and RMS means the filesystem is a simple database too.
DCL seems weird but all the commands work the same way, take the same arguments and so on. You can guess with a very high chance of being right. And if you can’t the help/error message is actually useful.
Rock solid stability. Generally very easy to manage, one sysadmin can do a lot.
What about Windows CLR/COM/UWP?
Curious about what you find being unmatched, as I never used VMS, beyond diving into its developer's documentation.
I don't know about how it works on VMS, but Microsoft's COM is the only other attempt of language interop I know of. Recently I implemented a COM server, added `IDispatch` to its interfaces and suddenly I could control and test it from Porwershell with no extra effort on my part. Like, magic.
VMS IPC was done via mailboxes, send a message to a person or a program was the same. Which sounds weird to anyone used to the way Unix does mail, but it worked very well.
(Yep, VAX BASIC was a serious language used for real, production applications)
Features of VMS like transparent clustering are missing, for example.
POSIX personality was the place for them.
Modern Windows follows mainframe's footsteps by providing UNIX compatibility via a VM environment.
Names can be quite different. I remember looking at the disk stack and thinking it looked quite similar, save for completion ports.
What is behind OpenVMS project - nostalgia or some pragmatic reasons?