Ken Olson had enough missteps at the time the writing was on the wall. Even at the time that would have been a clear waste of money to develop.

I know it ran on DEC equipment, but I don't recall a VMS version**. I recall my disappointment when I was moved to the Windows NT version. A lot of users were looking forward to Itanium before HP and Intel screwed that up for the HPUX side. At the time it seemed to be UNIX only and it still bears that mark, though a lot of changes to the outside interface have occurred to obscure them. I worked with Pro/Engineer when it was only usable on UNIX (HPUX, Solaris, Ultrix, et al). Being not-native makes porting easier, but then it doesn't fit so well on the target with user expectations one of the reason that Solidworks seems to feel better to those who like it.

Perhaps I'm mistaken but the last time I looked WF used almost no standard Windows dialog boxes, making interfacing with tools like AutoIt almost impossible.

I know that PTC originally split the underlying code from the GUI, such as MOTIF et al, so it could be ported among the various UNIXes with the resulting custom code for the supporting the interface moved to Windows. A certain big company has enough cash to port their office products, but I know they weren't designed to be portable and they don't do it for the income. Wordperfect was the last one to really make an effort. I am looking at about 30 years of software development and the small number of companies that have been able to support multiple OSs. How bad would it be? Sure, keep those options open.

Ptc creo parametric 5.0