[Info-vax] Updated HPE/VSI OpenVMS V8.4-2L1 Marketing Brochures

[David Froble]

IanD wrote:

> Where is Linux today compared to OpenVMS? Years ahead and the gap is growing

Linux has some large organizations doing development.  It's not just individuals.

> Where is Windows today compared to OpenVMS? Years ahead and the gap is
> growing

Weendoze has a large organization doing development.  It's never individuals.

> Please enlighten us on the following...
> 
> How do you think VMS is going to catch up or stop being left behind? Doing a
redhat perhaps? Redhat usurped open source indirectly by piggybacking on Linux
and open source and monetised it for their own profit. I'm merely advocating VMS
look to do something similar and piggyback on what is clearly working

What I'd like to see is some details on what's leaving VMS behind.  Yes, there 
is vast room for improvement.  But strictly for an OS, I tend to doubt these 
claims of "vast differences".

> Apart from existing customers, how do you propose to attract new customers to
> VMS? Through organic growth or tapping into an existing open source code base
> out
there? Which one do you think will create the largest growth and bring the
quickest dividends?

When looking at open source stuff, you need to ask, does it have any benefit for 
VMS?  Perhaps some of it might not.

> How do you propose to attract new developers to VMS? Do you have contacts in
> the education sector? I do and I can tell you with
100% certainly that open source virtually totally dominates here. Perhaps your
snide remark about brainwashing might have been better focused pointing out what
the education sector is doing to young minds when it comes to pushing ideas and
ideals because these are the people you need to attract to VMS

AS I've pointed out in the past, being exposed to VMS in education would be 
nice, but not essential.

> As for computing languages, the one's attracting the largest base of current
coders and future are in fact open sourced based one's or moving towards it

But, are those "current coders" doing anything worthwhile?

> Java will go some of the way to helping code being ported over the VMS but
it's hardly going to drive new innovation to be developed on the VMS platform.
> VMS will be a target for deployment not the home for software development for
> 
large scale projects other than specific projects targeting VMS itself and I
think that number will be tiny on actual VMS
> 
> Browse GitHub and see what's coming down the pipeline and then enlighten us
how VMS is going to be playing in these future arena's and working with even a
fraction of these endeavours without an open source presence and/or open source
focus or embracing open source?

Quantity is not the same as quality.  How many of those things do you have a use 
for?

> VMS is closed source and it appears the licence agreement will keep it that
way, that's ok but it doesn't mean that going forward open source cannot be
looked at for newer aspects of the OS or do you somehow think that VSI can keep
up with Linux with it's 10's of 1000's of contributors who are moving it's
innovation further along at an accelerating pace.

If there are 10s of thousands of coders for the Linux OS, how many lines of code 
are allocated to each, 2-4, maybe 5?

:-)

No, the core stuff is being done by a small core of people, probably most of 
them being paid for their work.

> Do you think VSI will keep pace with what's coming down the pipeline in
> Linux?
It's going to take VSI 2 - 3 years more just to move VMS to x86. What is Linux
going to bring to IT in this time?

That's a scary thought.  We can hope not too much ....

> On Sunday, October 2, 2016 at 5:40:59 PM UTC+11, Phillip Helbig (undress to reply) wrote:
>> In article <27c6e2e0-e540-4eca-bd63-78af2b48c780 at googlegroups.com>,
>> clairgrant71 at gmail.com writes: 
>>
>>> The VSI/HPE agreement does not allow us to make VMS open source.
>> And a good thing that is too.
>>
>> For the first time since sometime BEFORE the demise of DEC, VMS is in 
>> the hands of people who know it well and care about it.  While there is 
>> a fear that it might be too little too late, let's give them a chance 
>> and see what happens.
> 
> DEC failed, it's as simple as that

DEC failed because they could not trim the huge work force that the very 
expensive early computers supported.