Indeed. It's refreshing to see something that's not a Unix or a bastard child of VMS (even VMS is quite different from a Windows command line)

PowerShell brings some of it back! Though I do not think VMS had PowerShell (and Nushell)'s best feature; being able to pipe objects between commands, and not just text strings.

Having played with OpenVMS for a bit and suffering some of the steep learning curve, I'm not sure bringing forward more of the VMS heritage in Windows is the Right Thing To Do.

I think they should be. Top to bottom hardware and software co-design. I wish they hadn't gone object code only, because I feel like that really ended up causing a lessening of cool software coming out and a too heavy focus on vendor software (back in the old days, the systems programmers at customer shops often modified the operating system and would get those mods put into the OS by IBM for next release, now the sysprogs still modify the OS, but much less likely to be codesigned with IBM if you come up with something cool, and there is less visibility into the source for the OS kernel for z/OS).

But still, the hardware/software co-design and full system suite provided (FreeBSD style) kernel + OS attached really is a great way of doing things and the more I work in Mainframe and also work on Linux, the more I wish Linux vendors took more cues from the Mainframe or FreeBSD worlds.

I suppose you could argue that Oxide Computer is attempting this as we speak. One of the reasons I am a big fan of them.

All that and the fairly incredible amount of engineering that goes into the whole architecture, from processor, to memory system, to the numerous hardware assists. And build quality, because the machines are tested to work through earthquakes.