News for hackers. Stuff that matters.
Re:OpenVMS: state of the x86 port by ncmncm on Wednesday October 16, 2019 @12:46AM (#21267135)
I just hope they are doing drivers only for devices found in mainstream VMs. It would be a fool's errand to try to keep drivers up to date with real hardware. There is no practical benefit to anyone to run VMS outside a VM, but there are still important VMS applications that would run perfectly happily and reliably on maintained equipment in VMs forever.

IBM's AS/400 system (now called i series?) was designed for that from the start. There never was an AS/400 machine, it was always emulated. Programs started in the '80s are still running, migrated from one physical host generation to the next without ever being shut down.

Re:OpenVMS: state of the x86 port by kjs3 on Wednesday October 16, 2019 @05:38PM (#21276107)
There absolutely was, and is, an AS/400 machine. Originally, it was a custom (and kinda weird) CISC processor and associated specialized I/O architecture. Now it's a customized Power derived processor and a somewhat more standards oriented I/O architecture. There is an extremely well defined abstraction layer that the applications run on top of that allowed them to be migrated, but it's intimately tied to the physical implementation of the underlying AS/400 hardware.

I'm not an AS/400 expert, but did work in one of the largest AS/400 shops in the world for quite a while. The AS/400 folks definitely didn't live migrate apps CISC->RISC when they upgraded. Sat is lots of change management meetings there. Could they have? Dunno. But they sure operated like that was SOP.

Re:OpenVMS: state of the x86 port by ch_123 on Wednesday October 16, 2019 @09:57PM (#21278266)
Within the last few years, the IBM i systems use exactly the same CPUs as the AIX systems. In fact, I believe they sell the same models of servers to support both OSes.
Re:OpenVMS: state of the x86 port by mech422 on Wednesday October 16, 2019 @07:10AM (#21269097)
AS/400's were physical boxes - I worked on them back in the late 80s, as well as system/36(38?). They even had a PL/1 compiler, if you couldn't stomach RPG :-D
Re:OpenVMS: state of the x86 port by malux85 on Wednesday October 16, 2019 @02:02AM (#21267493)
Which VM software will allow you to migrate a running VM to another physical host without shutting down? That’s sounds awesome
Re:OpenVMS: state of the x86 port by snuxoll on Wednesday October 16, 2019 @02:05AM (#21267517)
Any of the ones frequently used for server virtualization? Live migration is a standard and pretty important feature.
Re:OpenVMS: state of the x86 port by jacobush on Wednesday October 16, 2019 @04:18AM (#21268183)
I guess IBM must have offered that since a long time ago. I always find that whatever is new under the sun, IBM did it a long time ago. And their name for it is always something else than what it's called nowadays.
Re:OpenVMS: state of the x86 port by stunthamsterio on Tuesday October 15, 2019 @03:49PM (#21262884)
I'm genuinely looking forward to this. I used VMS back in the 90's and loved it as an OS. Clustering, versioned file systems, reasonably well formed error messages; it seemed very civilised.

It'd be nice to be able to run it in a VM and see how much I've forgotten. I've got an old workstation in my loft, but haven't really got the room to have it setup.

Re:OpenVMS: state of the x86 port by icedchai on Tuesday October 15, 2019 @05:00PM (#21263695)
VMS Clustering was very interesting. It was basically baked in to all layers of the OS, if I remember. You could access devices, file systems, users, batch queues, processes, etc. across the cluster. It felt very well designed.
Re:OpenVMS: state of the x86 port by stunthamsterio on Tuesday October 15, 2019 @05:13PM (#21263861)
That's one of my enduring memories of VMS, and something that came as a shock when I came to different OS - the lack of clustering. We had (As far as I remember) two vast servers called Alpha and Beta (With Gamma as a dev server). They were the size of a full-size rack for a single server. But from a developer perspective, my processes would run seamlessly across both of them and see a single FS, a single set of processors and RAM.

That and developing in Vista4GL. I'd kill to get hold of some manuals for that to remind myself what my first professional language was like.

Re:OpenVMS: state of the x86 port by icedchai on Tuesday October 15, 2019 @06:55PM (#21264908)
DEC had some innovative ideas with VMS, for sure... 40 years later, we still don't see anything quite like its clustering with Unix / Linux. I'm happy VMS Software is keeping it alive.
Re:OpenVMS: state of the x86 port by bitwize on Tuesday October 15, 2019 @10:13PM (#21266403)
You do see something like it with Plan 9.
Re:OpenVMS: state of the x86 port by jakeogh on Tuesday October 15, 2019 @07:29PM (#21265244)
Anyone familiar enough with plan9 resource sharing to compare the two?
Re:OpenVMS: state of the x86 port by dekhn on Tuesday October 15, 2019 @04:54PM (#21263633)
I used TruCluster (late 90s thru 2006) which was Tru64 UNIX (from DEC UNIX), I think it shared a lot of tech with VMS clustering. Many interesting ideas, such as being able to write to the filesystem with a guaranteed IO rate from any cluster node (100MB/s at a tiime when that was a lot) and many other things that are less interesting after you rewrite your software around not needing clustering.
Re:OpenVMS: state of the x86 port by CaptainZapp on Tuesday October 15, 2019 @04:36PM (#21263443)
HELP is your friend.

The VMS help system, while far less verbose than Unix man pages was, thanks to its hierarchical organisation really, well, helpful.

Re:OpenVMS: state of the x86 port by LinuxBender on Tuesday October 15, 2019 @04:40PM (#21263490)
Remember the bug / update that shortened (H)elp to Halt? :-) Some here for sure have to remember that one.
Re:OpenVMS: state of the x86 port by dekhn on Tuesday October 15, 2019 @04:56PM (#21263654)
the VMS HELP system was my introduction to "learn a system by using depth-first HELP". I also recall eventually coming across the page which explained dynamic linking (I couldn't even link hello world with my 2 block disk quota).
Re:OpenVMS: state of the x86 port by CaptainZapp on Wednesday October 16, 2019 @01:04AM (#21267212)
Same here.

My basic introduction was that my boss sat me in front of a VT220 terminal and told me about the HELP command.

Later I discovered the absolute awesomeness that was VMS (at that time, OpenVMS came later) documentation.

For me and to this day it's the benchmark how documentation should be written an organized.

Re:OpenVMS: state of the x86 port by netrap on Tuesday October 15, 2019 @04:23PM (#21263299)
They do have a free hobbyist VM on their website.

https://training.vmssoftware.com/hobbyist/

Re:OpenVMS: state of the x86 port by ngcc_hk on Tuesday October 15, 2019 @10:55PM (#21266632)
128 MB memory. The alpha emulator. Suddenly wake up.

Still remember for old time sake do some 360 assemble on an emulator. Suddenly I aware that is 16 MB not GB ... and I use a 24 MB one to support thousands of users in 1980s.

Those really were the days.

Re:OpenVMS: state of the x86 port by stunthamsterio on Tuesday October 15, 2019 @04:29PM (#21263366)
Oh nice tip, I didn't know that - Now I'll have to see if I can run a VMS VM inside my Windows VM... Turtles all the way down.
Re:OpenVMS: state of the x86 port by snuxoll on Tuesday October 15, 2019 @04:30PM (#21263388)
Would be humorous considering the NT platform was heavily inspired by VMS.
Re:OpenVMS: state of the x86 port by pjmlp on Wednesday October 16, 2019 @01:24AM (#21267307)
To the point that one can find similar APIs when reading VMS documentation.
Re:OpenVMS: state of the x86 port by EricE on Wednesday October 16, 2019 @04:03PM (#21274861)
Yup - having started with early Mac's and PC's in the late 80's and 90's, running into VMS in the 90's and experiencing a "real" operating system was an eye opener. The versioned file system was so cool and obvious I can't believe it never caught on with other platforms. Much nicer than snapshots since it was at the file level (different solutions for different problems!)

I bet VMS's versioning could have been the foundation for a fast, powerful and reliable de-dupe too. Hmm...

Re:OpenVMS: state of the x86 port by tapland on Tuesday October 15, 2019 @07:49PM (#21265414)
Yay!

I hammer at OpenVMS for 40+ hours/week and this is exciting!

We hit 99.99% uptime with new software features being installed being the reason for the downtime we've had (except for one instance a bunch of years ago, but at that time I would have been in middle school. I do worry about a slowly increasing reaction time to user actions though.

Running on X86 we wouldn't have to worry about the future.

Re:OpenVMS: state of the x86 port by yjftsjthsd-h on Tuesday October 15, 2019 @08:01PM (#21265512)
> I hammer at OpenVMS for 40+ hours/week and this is exciting!

What's your work like? Or perhaps I should say, what kind of company do you work at to use it?

Re:OpenVMS: state of the x86 port by tapland on Tuesday October 15, 2019 @08:12PM (#21265593)
We store the critical customer data (their personal info, what they are paying us for and their settings), build the interfaces for customer service, apis for s that are used on customer web/apps and logic for what is to happen for each call. I'm a dev but including our devs, database and hardware people we are less than 0.05% of the company employees.

I'm the youngest and almost everyone is 2x+ my age. We've lost 40% of the team to retirements since I joined two years ago.

It's a tight team but communication is oh so inefficient whenever someone is working remote and between our two locations.

We have other services now that we make calls to to get for example mail and email sent to customers, but now and then I still see customers receiving plain text email from the production machine D:

Re:OpenVMS: state of the x86 port by mariuolo on Wednesday October 16, 2019 @07:16AM (#21269134)
How good is this for your CV? Do you see yourself working with this tech for the next 20+ years?
Re:OpenVMS: state of the x86 port by tapland on Wednesday October 16, 2019 @03:06PM (#21274153)
I have no idea how good it is. Probably not very, but it's a decent paying job where I live, upper levels of what devs make.

I studied business and management. Maybe that will be a pro for a new role if they shut down the VMS.

Re:OpenVMS: state of the x86 port by PeCaN on Tuesday October 15, 2019 @10:58PM (#21266643)
How'd you find a VMS job anyway?
Re:OpenVMS: state of the x86 port by tapland on Wednesday October 16, 2019 @02:39AM (#21267687)
A company posted a listsing looking for COBOL developers. I thought it would be mainframe and contacted them but they were running OpenVMS.
Re:OpenVMS: state of the x86 port by flomo on Wednesday October 16, 2019 @03:25AM (#21267940)
Awesome, you have a career for life, until you don't.
Re:OpenVMS: state of the x86 port by retrocryptid on Tuesday October 15, 2019 @06:36PM (#21264749)
A couple years ago I set up VMS on a VAX emulator on Raspbian. In case you're interested, here's the link describing the process:

http://www.wherry.com/gadgets/retrocomputing/vax-simh.html

And I guess the process of requesting and installing a license changes from time to time. This page describes a slightly different process for activating the license which worked for me:

https://meadhbh.hamrick.rocks/home/technical-sh-t/installing...

Re:OpenVMS: state of the x86 port by jerzyt on Tuesday October 15, 2019 @10:46PM (#21266570)
While security is being mentioned as one of the strengths, and I certainly agree with that, there was a version of VMS in the late 80s which wouldn't let you create a password if another account already used it. In a small department it wouldn't take more than 15 minutes to hack into someone's account.
Re:OpenVMS: state of the x86 port by ngcc_hk on Tuesday October 15, 2019 @10:51PM (#21266609)
Wow. That is security measure so stupid never heard before. Really :-)))))
Re:OpenVMS: state of the x86 port by dang on Tuesday October 15, 2019 @03:29PM (#21262662)
Re:OpenVMS: state of the x86 port by ch_123 on Tuesday October 15, 2019 @04:42PM (#21263500)
A related presentation from a few months ago which goes into some extra detail: http://vmssoftware.com/pdfs/webinars/X86_OpenVMS_V9_0_Update...
Re:OpenVMS: state of the x86 port by dwheeler on Tuesday October 15, 2019 @04:54PM (#21263630)
It's cool that this exists. I might even try to port a program to it, for my own amusement. But I don't see the big draw.

VMS had its pros and cons as compared to Unix/Linux. VMS' help system is really nice. However, VMS filenames are baroquely complex (yes, automatic versioning can be nice, but the rest of it was insane). Even at its height, VMS lost to Unix, and Unix plus Linux are now completely dominant in the areas VMS once filled and has had decades to fill in missing capabilities. I don't see what the big draw of VMS would be over Unix/Linux, at least enough to justify it. The world doesn't need another proprietary operating system, especially one incompatible with what people have now been doing for decades.

Re:OpenVMS: state of the x86 port by speleo_engr on Tuesday October 15, 2019 @05:39PM (#21264154)
I don't think its going to get any design starts, nor is that the intent. There are companies with rock solid legacy applications that want to continue to run them on newer hardware. VMS first ran on the VAX (long dead), then Alpha (dead), and finally Itanium (recently dead). x86 will let these legacy apps run for a few more decades.
Re:OpenVMS: state of the x86 port by technofiend on Tuesday October 15, 2019 @07:59PM (#21265494)
As much as anything I believe it's a mix of nostalgia and appreciation for what came before. I don't think anyone is suggesting Amazon crank up micro VMS instances for taking on modern workloads. Although as the person below me suggests there may also be a niche market for hosting legacy applications a little while longer.
Re:OpenVMS: state of the x86 port by LinuxBender on Tuesday October 15, 2019 @04:39PM (#21263478)
This used to be my favorite OS. I am pleasantly surprised to see it is still around. The security model at the time was vastly superior to Unix. I maintained the SMS gateway for a mobile provider on it. OpenVMS on Alpha had incredible performance and stability compared to the Unix system counterparts at the time. (comparing rack space real estate that is)
Re:OpenVMS: state of the x86 port by EricE on Wednesday October 16, 2019 @04:12PM (#21274952)
Alpha was an amazing platform. Yet another great technology that HP flushed because they didn't know what to do with it :(
Re:OpenVMS: state of the x86 port by vkaku on Tuesday October 15, 2019 @09:24PM (#21266109)
I'm totally looking forward to this. I got access to the VAX and Alpha kits from HPE, but I've always wanted to run it natively on x86. :) OpenVMS rocks.
Re:OpenVMS: state of the x86 port by aarroyoc on Tuesday October 15, 2019 @04:05PM (#21263071)
I'm very interested to know why this port is taking so long. Few human resources? Not a priority? Lots of assembly code?
Re:OpenVMS: state of the x86 port by skissane on Tuesday October 15, 2019 @04:38PM (#21263473)
> I'm very interested to know why this port is taking so long. Few human resources?

That would be my guess. I don't know how big VMS Software is, but I doubt they are that big. The market they are addressing is limited in size, and is almost certain to shrink rather than grow, so it would be difficult to justify a massive investment in developers.

OTOH, how long did the VAX->Alpha port take? How long did the Alpha->Itanium port take? How long would have HP taken if they'd decided to commit to an x86 port themselves?

Re:OpenVMS: state of the x86 port by ch_123 on Tuesday October 15, 2019 @05:04PM (#21263750)
See:

http://www.dtjcd.vmsresource.org.uk/pdfs/dtj_v04-04_1992.pdf (page 113 of the PDF)

http://www.decus.de/events/alphamigration/vortraege/porting_...

It sounds like both took about two years to reach first boot on the target platform. Both involved considerably more people and resources than the VSI port to x86.

Re:OpenVMS: state of the x86 port by eej71 on Tuesday October 15, 2019 @05:05PM (#21263756)
re: VAX->Alpha

I don't know when they started it - but it was available to customers late 1994 if memory serves.

The Itanium port was announced Sep 2001? A usable version for customers to deal with - spring 2005?

Re:OpenVMS: state of the x86 port by icedchai on Tuesday October 15, 2019 @05:11PM (#21263834)
Also consider DEC and HP had enormous engineering organizations. And Alpha was designed as extension of the VAX architecture, so presumably the port was less complicated. You can still find references to "EVAX", for "Extended VAX" in some of the headers, along with the EV* CPU model numbers. Itanium I know less about...
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.
Re:OpenVMS: state of the x86 port by dfboyd on Tuesday October 15, 2019 @06:42PM (#21264809)
Isn't the VMS x86 port called "Windows NT"?
Re:OpenVMS: state of the x86 port by ithkuil on Wednesday October 16, 2019 @04:57AM (#21268387)
Technically Cutler and his team first targeted Intel i860 (N10) and designed the NT kernel multi-arch from the ground up.
Re:OpenVMS: state of the x86 port by Fnoord on Wednesday October 16, 2019 @08:01AM (#21269439)
An abomination is what the successor WNT is to VMS.
Re:OpenVMS: state of the x86 port by anticensor on Wednesday October 16, 2019 @03:25AM (#21267932)
Is x86 port of OpenVMS ReactOS, then?
Re:OpenVMS: state of the x86 port by jki275 on Tuesday October 15, 2019 @07:09PM (#21265034)
This!
Re:OpenVMS: state of the x86 port by retrocryptid on Tuesday October 15, 2019 @04:06PM (#21263075)
What serendipity! I was looking at this page last night, looking forward to 2020. Also happy to hear there are at least a few VMS fans here.
Re:OpenVMS: state of the x86 port by icedchai on Tuesday October 15, 2019 @04:48PM (#21263555)
One of the first multi-user systems I worked with ran OpenVMS, so I have a fondness for it and related nostalgia... DECnet, VAX BASIC, etc. I've run it at home on Alpha and VAX emulators.
Re:OpenVMS: state of the x86 port by unixhero on Tuesday October 15, 2019 @04:02PM (#21263031)
What will it cost???
Re:OpenVMS: state of the x86 port by snuxoll on Tuesday October 15, 2019 @04:31PM (#21263395)
If you are a hobbyist, nothing, assuming they keep the hobbyist program (and I assume they will).
Re:OpenVMS: state of the x86 port by pmlnr on Tuesday October 15, 2019 @06:03PM (#21264430)
Everything.

Joke aside, I have no idea how VMS will be run on non hard-realtime hardware.

Re:OpenVMS: state of the x86 port by unixhero on Wednesday October 16, 2019 @04:45AM (#21268321)
Cool. Do you have any links to real time hardware of the past?
Re:OpenVMS: state of the x86 port by mongol on Tuesday October 15, 2019 @04:38PM (#21263474)
I needed to "get around" on OpenVMS in a previous assignment. Some java processes executed there and needed my attention from time to time. I never became good friend with it and never "saw the light". I much prefer Linux.
Re:OpenVMS: state of the x86 port by dingosity on Tuesday October 15, 2019 @07:15PM (#21265103)
I think we all prefer what we're most familiar with. VMS hearkens back to an era before tab completion was common and it still throws me when I have to type DIR instead of ls.

But... VMS does have some interesting features. Even if you prefer Linux, it's interesting to compare the two and read about why the VMS designers did what they did.

Re:OpenVMS: state of the x86 port by burnte on Tuesday October 15, 2019 @03:46PM (#21262846)
I can't even imagine why VMS is relevant in 2019.
Re:OpenVMS: state of the x86 port by retrocryptid on Tuesday October 15, 2019 @04:12PM (#21263163)
To follow up on the previous reply, there are OpenVMS instances that have uptimes measured in decades. Not everyone needs this; in the past 20 years we've all learned how to distribute applications onto arrays of consumer PCs. But for some organizations and some applications, long uptimes are a BIG DEAL(tm).

Also... VMS makes sense in a way that Unix never did.

Re:OpenVMS: state of the x86 port by defined on Tuesday October 15, 2019 @06:48PM (#21264858)
Now just run Erlang on VMS and you have an uptime match made in heaven :)
Re:OpenVMS: state of the x86 port by youdontknowtho on Tuesday October 15, 2019 @03:54PM (#21262929)
Applications that run on OpenVMS tend to be really important and have been in continuous operation (including upgrades where new ISA's were introduced) for decades. It was ported to Itanium and missed out on taking advantage of the 64-bit x64 wave. As Intel has moved high end reliability features to the Xeon line OpenVMS applications can be moved over to modern hardware.

It's not so much that it's relevant to everyone, but it's a super interesting topic watching it get ported.

Re:OpenVMS: state of the x86 port by goatinaboat on Tuesday October 15, 2019 @03:48PM (#21262873)
Linux today can’t do half of what VMS could do in 1999.
Re:OpenVMS: state of the x86 port by thelazydogsback on Tuesday October 15, 2019 @04:13PM (#21263182)
Maybe in some respects. Though I don't remember too much VMS, I know enough to remember what a god-send the Unix shells (and associated stdio tools) were compared to other command environments spawned (pardon the pun) by batch systems. (The versioned files were both cool and annoying FWIR)
Re:OpenVMS: state of the x86 port by StreamBright on Tuesday October 15, 2019 @04:47PM (#21263548)
And 10-100x the number of lines of code.
Re:OpenVMS: state of the x86 port by turk73 on Tuesday October 15, 2019 @07:23PM (#21265186)
I don't think it is possible to back up that statement. In 1999, machine interoperability was not as critical as it is today.

Last time I worked with OpenVMS was 2014 going into 2015. The system in question was an orders management system for an online pharmacy. It. Was. Hell. The Alpha-based cluster was being rebooted daily because it would run out of memory constantly. They would purchase spare parts for their cluster from a local company that specialized in NOS and recovered boards bought on eBay. We had some laughs about that!

The code was ancient--some of the earliest comments in the sources dated to the 1970s. There was no source control, no modern compiler, no debugger, no anything. We used sockets to communicate to a sort-of SOAP service to get data out for reporting but it was incredibly, tearfully s-l-o-w.

The UI was terrible. The users of it complained endlessly, and rightly so. We're talking about a time when most everything out there was built on a HTML Web-based system for at least a decade already and people were well used to Web interfaces. And here these poor souls were still using terminal emulators to connect to a green screen application and had to to have all kinds of odd work-arounds and policies to get by with all the bugs and strange anomalies. Did I mention the horrible uptime?

The management kept wanting more, more, more out of the enterpise Java team but all the technical limitation were on the VMS side. Meanwhile, the syadmin who ran it was a complete turd of a human being, only trying to keep his job there lest he be forced into retraining into some actually useful technology. Worse, he actively campaigned against any technical changes we wished to make (for fear of losing his fiefdom) and so undermined my team to the point where management became openly distrustful of us. "Can't trust that new-fangled Java stuff!" "You mean the actually reliable, high-performance stuff? That stuff?"

The company unbelievably doubled down on this odious mess by purchasing the source code for the system from the vendor that owned because that vendor wanted to wash their hands of it and get out from under the hell of supporting it. When I heard what my company paid for that code I nearly had a breakdown because it was eye-watering. I could have re-written the thing 5X over and extracted the data for that kind of coin. If that's the kind of idiocy it takes to manage a large corporation in America these days then I should be a CEO because I am far more than qualified! I could show up one day a week and do less damage. Had I had a free hand at that company I could have done incredible things, but it was not to be.

Worse still, now that they owned the sources, they thought they could do something useful with it and hired a contractor who had once sort of worked on this same trash at another firm. He was charging $250/hr to be there and was the most obnoxious developer I have ever worked around. He set the bar very low on personal hygiene, decorum, and general bad behavior around the office. They had to move him out of the cubes and give him his own room because of so many complaints about odors and um, noises.

Looking back, it seems like everything related to VMS was these kind of obnoxious people--I used to hang out with the sysadmins who managed the clusters at the college I attended and they, too, had that VMS/DEC obnoxiousness disease. I don't get it, I'll never get it, am happy to be far away from it. DEC had its day, they failed to adapt and modernize and went away. You don't see this same nostalgia for Wang Computers and Wang was the true original in the mini space.

Re:OpenVMS: state of the x86 port by goatinaboat on Wednesday October 16, 2019 @01:52AM (#21267438)
This is kind of a weird story bro. Like you’re at a deeply dysfunctional organisation with management and coworkers that you hate (maybe for good reason) but your anger is directed towards an OS that even running on junk hardware is still making your company money with perfect backwards compatibility over 40 years? Huh.