I must admit that most of this thread has followed the normal Windows/UNIX path, leading to name calling.
It is interesting to be reminded of another OS that in it's own way has shaped what we have today.
VAX/VMS is an interesting OS, and in many ways my second favorite OS to UNIX. What you have said of VMS is quite true, but some of the assertions you have made about UNIX are wrong.
As someone who learned UNIX back in the late '70's and then took a spell of sysadmin'ing RSX/11M and eventually some VAX/VMS, I agree that the batch and spooling systems on VMS were much better, because DEC had Tops 10 and Tops 20 as a good model to work from. But RSX/11M's batch system was not as good as the UNIX at/batch commands, but that is because RSX/11 was not really a general purpose OS. In the UK RSTS/E was the main commercial PDP/11 OS, and very little of that mad it into VMS. If you remember that far back, you will find that VMS version 1 was really just a 32 bit port of RSX/11M, complete with non-hierarchical file system, and limited Files/11 support.
The backup and restore, I'm not so sure that BRU and Backup/Restore was hugely better that Fbackup, Frestore, Finc and Frec on generic AT&T UNIX systems, but these fell by the wayside.
It is quite clear that Files/11 (which was a layered product on RSX/11) and the VAX filesystem (I know it had a name, but I can't remember it at the moment) suited commercial use for VAX, including file and record locking, but that does not mean that there was nothing similar in UNIX. UNIX version 7 included a thing called the "Multiplexed file system". This allowed you to add all sorts of functionality to the standard file system. But the standard byte addresses file interface allowed you to implement pretty much any functionality anyway, including arbitrary sized record structure, and there were add-ons like C-isam, which was available as a library on most UNIX variants (OK 3rd party software), which was for a time a near industry standard for UNIX.
AT&T's UNIX from System 3 also had mandatory file and region locking for files in a filesystem. This was not carried into the BSD variants as far as I remember, until the SVR4 merged system that provided cross-fertilization between major UNIX variants.
It is interesting that people also overlook the RFS filesystem that came as part of SVR3.2 and later. This was a highly stateful distributed filesystem that implemented 100% of UNIX filesystem semantics, including the mandatory locking protocols. I'm fairly certain that if you came across UNIX from a BSD/SUN route, that you almost certainly never came across this advanced filesystem which again, fell by the wayside.
It is not directly comparable with VAX Cluster, which was a groundbreaking way of making your environment more that the sum of the machines in it, but this was an add-on to VMS, and if I remember correctly, quite expensive for commercial use.
VMS was good. It's DCL CLI was very helpful to novice users, utilities like EVE and TPU were very good for University work, and the wide variety of vendor provided applications. It had the demand paging system that other vendors aspired to. But DCL had it's own limits. If I remember correctly, in order to get the argument processing working for your application, you had to produce a prototype file so DCL could parse the arguments for you, whereas letting the application manage it's own arguments
But I would contend that although it was very suitable for many types of work, ultimately it was not as flexible or as widely deployed as UNIX. Although you could say that the WorldBox MicroVax II was a microprocessor based system (I was at the UK site of the World launch event in Harrogate), that there were personal VAX Stations, and there were some very large VAX systems, UNIX appeared on everything from desktop PC's (like the AT&T 3B1 and even PC/ATs if you count Xenix/286 as a UNIX) through to the largest mainframes of the time from the likes of IBM and Amdahl. And I haven't seen a HPC cluster running VMS, as I have with COS (at one time Cray's UNIX) and AIX (IBM's UNIX variant).
Don't get me wrong. I'm not criticizing VMS. As I said, it is one of my favorite OS's. But it is like comparing apples with pears. They are similar, but there are significant differences which mean some people like apples, and some pears. I would say that there is probably still a place for VMS, but it has become niche, in the same way that genetic UNIX is going. But UNIX has a direct successor that will keep the line going in Linux.
Maybe you ought to be pressing HP to license VMS with an open license. I think that that is the only way to stop it dying a slow and lingering death.