[Info-vax] VMS survivability
Dan Cross
cross at spitfire.i.gajendra.net
Sat Feb 18 22:06:20 EST 2023
In article <tsrpoc$5qhq$2 at dont-email.me>,
Arne Vajhøj <arne at vajhoej.dk> wrote:
>On 2/18/2023 5:08 PM, Dan Cross wrote:
>> In article <tsrf3b$4krc$1 at dont-email.me>,
>> Dave Froble <davef at tsoft-inc.com> wrote:
>>> What benefits do you imagine for VSI, for customers,
>>> if VSI were to do what you suggest. Talking about
>>> the "open source" issue.
>>
>> Establishment of a developer ecosystem, crowd-sourced fixes for
>> bugs, security auditing,
>
>That all sounds very nice.
>
>But how does it work for the VMS stuff that are already
>open source?
>
>I can tell you: two handful of people are doing all the
>work.
Yes. Because there is no incentive for anyone else, because VMS
is clinging to an antiquated closed model and maintainers see it
as a dead platform. Do you not see that as a problem?
>It is problematic to find people to maintain the ifdefs
>and build scripts of for VMS in many open source projects.
Have you ever stopped to wonder why that is, and how one might
go about changing it?
>Expecting the community to do serious work on 25 MLOC
>is unrealistic.
It is unrealistic to expect VMS to be able to compete against
Linux with the current model. It's a shame that so many VMS
users are perfectly ok with that.
- Dan C.
More information about the Info-vax
mailing list