[Info-vax] VMS Software: New US Mailing Address
Bill Gunshannon
bill.gunshannon at gmail.com
Wed Oct 12 10:27:38 EDT 2022
On 10/12/22 09:05, Simon Clubley wrote:
>
>
> Unfortunately, when architectures are changed not all packages make it
> across to the new architecture.
And the result is the loss of even more customers. How many can VMS
afford to loose?
>
> For example, VAXELN was abandoned when the move to Alpha occurred and
> it looks like there will be no Ada compiler for x86-64 VMS.
That's just silly. VAXELN was tied to the VAX architecture it would
have been abandoned no matter what architecture VMS moved to.
>
> The question is, just how major are the packages that are being lost ?
How major they are is dependent on the user, none of them are really
major to VSI.
> Oracle Classic is a major example of something that has been lost, but
> that's tied to VMS in general, not just x86-64 VMS.
>
> There's been no negative comments about Rdb recently, so I assume that
> is still on course for release on x86-64 VMS. Of course, if Rdb wasn't
> released for x86-64 VMS then that would be a very serious blow to VSI's
> plans.
A database is the least serious of these problems. VSI could easily
(well, maybe not easily) decide that Postgres was going to be the VMS
database just like RDB was, at one time, a DEC product. It is easily
a suitable replacement for either Oracle or RDB. Just suffers from NIH
syndrome.
>
> So the question is, of the other packages Marc uses, how many of them
> are in general use within the VMS user base as a whole ?
Doesn't really matter if the loss of these means they can't or won't
move forward on VMS.
bill
More information about the Info-vax
mailing list