News for hackers. Stuff that matters.
Re:OpenVMS: state of the x86 port by altmind on Tuesday October 15, 2019 @04:05PM (#21263068)
What are the things VMS did the best? How it compares to linux nowadays?

What is behind OpenVMS project - nostalgia or some pragmatic reasons?

Re:OpenVMS: state of the x86 port by goatinaboat on Tuesday October 15, 2019 @05:42PM (#21264196)
It’s still unmatched for seamless language interoperability.

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.

Re:OpenVMS: state of the x86 port by pjmlp on Wednesday October 16, 2019 @01:27AM (#21267321)
Even when comparing against IBM i and z/OS language environments?

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.

Re:OpenVMS: state of the x86 port by zvrba on Wednesday October 16, 2019 @01:41AM (#21267377)
> It’s still unmatched for seamless language interoperability.

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.

Re:OpenVMS: state of the x86 port by goatinaboat on Wednesday October 16, 2019 @01:47AM (#21267406)
I’ve used COM (and before that CORBA) but these operate at a different level of abstraction. On VMS calling a Pascal function from FORTRAN “just worked” and then you could pass the return value to a C function or BASIC and it was fine.

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)

Re:OpenVMS: state of the x86 port by yellowapple on Tuesday October 15, 2019 @04:16PM (#21263217)
The more relevant point of comparison would actually be Windows, given the extensive design similarities between Windows NT (and thus, by descent, modern Windows) and VMS: https://everything2.com/title/The+similarities+between+VMS+a...
Re:OpenVMS: state of the x86 port by snagglegaggle on Tuesday October 15, 2019 @06:11PM (#21264500)
A lot of modern Windows kernel API looks exceedingly familiar to Unix. I would think perhaps early Windows was close to VMS, but as they tried to bolt on a POSIX layer it seems it has drifted.

Features of VMS like transparent clustering are missing, for example.

Re:OpenVMS: state of the x86 port by pjmlp on Wednesday October 16, 2019 @01:32AM (#21267346)
Window kernel APIs have nothing UNIX like beyond sockets.

POSIX personality was the place for them.

Modern Windows follows mainframe's footsteps by providing UNIX compatibility via a VM environment.

Re:OpenVMS: state of the x86 port by abotsis on Wednesday October 16, 2019 @01:22AM (#21267302)
Which api’s specifically? VMS was always (and still is?) posix compliant, as was nt. VMS even ran x11!
Re:OpenVMS: state of the x86 port by wbl on Wednesday October 16, 2019 @02:05AM (#21267522)
The I/O model in the kernel is very similar and utterly unlike Unix.
Re:OpenVMS: state of the x86 port by snagglegaggle on Wednesday October 16, 2019 @02:25AM (#21267618)
As you move up the stack it looks more Unixy. The core is VMS-like and I can see the similarity, but it seems to me the majority of the code actually written exists in a middleware layer that is maybe not as far from VMS as Linux, but not quite VMS.

Names can be quite different. I remember looking at the disk stack and thinking it looked quite similar, save for completion ports.

Re:OpenVMS: state of the x86 port by wbl on Wednesday October 16, 2019 @11:59PM (#21278793)
Softirq and taskqueue change the model to be more VMS like.
Re:OpenVMS: state of the x86 port by LinuxBender on Tuesday October 15, 2019 @04:46PM (#21263543)
Best? Stability. (In my opinion and experience) I never saw OpenVMS crash. I was never paged for an OpenVMS / Alpha system being offline.
Re:OpenVMS: state of the x86 port by eej71 on Tuesday October 15, 2019 @05:07PM (#21263776)
I have. Lots of times. Depends on what abuse you heap on them. And yes, been paged for nodes crashing, hung clusters, etc.
Re:OpenVMS: state of the x86 port by eej71 on Tuesday October 15, 2019 @05:11PM (#21263840)
The pragmatic reason is that there are enough organizations out there that depend on it and porting away from it is expensive enough that it is cheaper to stay.
Re:OpenVMS: state of the x86 port by turk73 on Tuesday October 15, 2019 @07:01PM (#21264954)
Nothing, really. The world moved on but a lot of fanbois didn't. I learned to code C on a VT420 and used VMS for quite a few years, many professionally. I never felt it was anything superb at all. As soon as I learned UNIX (and I've used every brand and flavor of it), there was just no comparison at all. SunOS and later Solaris were my favorite until Linux matured.