[Info-vax] OpenVMS app development, kitting

[Simon Clubley]

On 2021-11-24, Dave Froble <davef at tsoft-inc.com> wrote:
>
> As I read posts here in c.o.v, some of which deplore some of the parts of VMS, 
> as in the recent discussion about ASTs and the R0,R1,etc arguments, I have to 
> wonder what might happen to an "open" VMS.  Might some of the fanatical 
> "do-gooders" start upgrading or replacing some of the things that makes VMS 
> upward compatible?  Might some C programmers decide they didn't need Macro-32, 
> Basic, Fortran, Cobol, and such?  Might the desire for OO make many existing 
> applications no longer usable?  Where might such a thing go?
>

Due to the monolithic mass of integrated code which is _not_ cleanly
broken into clean interfaces, upgrading the internals of VMS is massively
harder than doing the same things elsewhere.

For one really simple example, adding a new filesystem to Linux is easy
(and can be done by end user organisations) because Linux has a nice
clean internal filesystem architecture.

VMS is a monolithic ugly mass of intertwined filesystem code by comparison.

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.