[Info-vax] 64 bit DCL ?

[David Froble]

Stephen Hoffman wrote:
> On 2015-01-18 20:27:50 +0000, David Froble said:
> 
>> Stephen Hoffman wrote:
>>> On 2015-01-18 14:50:13 +0000,   VAXman-  @SendSpamHere.ORG said:
>>>
>>>> Fuck that.  If you want Linux, get linux.
>>>
>>> Running Unix is easier in many ways, as that's where the more 
>>> powerful tools are.   That's also what VMS is competing with.
>>
>> Not here ....
> 
> Would you pick VMS for a wholly new development team that's performing a 
> wholly new application deployment project?

Trick question, and you already know that I'm rather biased.  But, let's 
look at that very valid question.

First, I'd have to have some feeling that VMS would not disappear on me. 
  VSI might be that assurance.

Next, what is the application?  If it's strictly a web server, probably 
not, but that isn't really a new application.

I know what I can do with VMS, even with it's aging warts.  So, I 
personally would be biased toward what I know.

I do not use *ix, do not know how to use it, and so would be prejudiced 
against it.  Sort of similar to the*ix user's prejudice against VMS.

If I needed a GUI, then at least that part of the application would not 
be on VMS.  I believe that has been called client / server.

There is also the question of whether I could put together a team that 
knew enough to do a decent job on VMS.

If I choose Apple or another *ix, I fear that the dreaded C would get 
involved ....

I did a project on weendoze maybe 15 years ago.  Actually, a 
re-implementation (hard) of a system I first developed in 1985 for 
PDP-11, and ported to VAX/VMS (very easy) in 1992.  Weendoze had some 
useful features, and it also lacked some things.  Regardless, the 
weendoze work took 1.5 to 2.5 times the effort that the same job would 
take on VMS.  Why pay more, stick with VMS.

>   If you do, that's great. 
>  But that choice is just is not very common.   If VMS is to grow, then 
> it needs to compete with what the other platforms provide.   That means 
> VMS must interest new customer sites, and must have the support expected 
> for and necessary for wholly new application deployments.

Yep.  Fix the deficiencies, if we can agree on just what they are.  Add 
needful things, if we can agree on what they are.

In my opinion, still a valid platform, with a good environment and 
tools, if VSI is successful.