[Info-vax] eCube OpenVMS survey

[IanD]

On Tuesday, February 17, 2015 at 10:47:42 PM UTC+11, Paul Sture wrote:
> Quoted from <http://blog.ecubesystems.com/2015/02/12/openvms-survey/>
> 
> -- start quote ---
> OpenVMS Survey
> Posted on February 12, 2015 by ecubeblog	
> 
> With the licensing of OpenVMS to VMS Software, some of the uncertainty
> in the OpenVMS industry has been eliminated. Does VMS Software's
> commitment to OpenVMS have any impact on your company's decision to stay
> on OpenVMS? Are there other factors that are impacting your decision to
> stay or move off of OpenVMS?
> 
> eCube is conducting a brief survey in order to:
> 
>     Get a better understanding of the market.
>     Better align NXTware Remote with the needs of the OpenVMS Community.
>     Learn more about the features you want in future versions of OpenVMS.
> --- end quote ---
> 
> 
> -- 
> 1972 - IBM begins development on its last tape drive (3480) ever because
> of the declining cost of disk drives.

The new CEO of MS is on a quest to have Windows play nicely with everything it can, or so it seems. Linux now represents 20% of MS azrues revenue stream, MS cannot afford to ignore linux any longer and it's driving changes in how MS play with others

In the process of opening up windows, there might be an opportunity to piggy back vms development on visual studio / .net

This is the threat I see from MS, that MS are becoming easier to deal with, easier to integrate with. A wolf in sheep's clothing?

I was not trying to imply that MS have VMS specifically in their sites, I suspect they couldn't care about it at all, believing that HP has buried it well and truly through neglect, but rather that VMS is getting caught in the crossfire as MS open's itself up to play nice with the rest of the world 

They are integrating everything, from development to production to enterprise wide to cloud and they have embraced the mobile platform now even in their exchange product and the visual studio platform is very much key to how they are tying it together. If it's possible for vms to piggyback on visual studio then it could be looked at

I agree with you, linux probably is the threat MS wants to mitigate the most, it still commands the lions share of the DC and to combat this MS imo have switched tactics, they are no longer demanding people choose which camp they want to live in but are pushing to get the message out that they will play with any camp you want. The MS ceo recently made specific comments that 'MS love's linux!' That's an about face if I ever saw one. The truth about how much MS loves linux is probably less than the lip service given but it's the first time MS have ever acknowledged linux other than a scornful rebuttal

I was not trying to say that .net was what we need on VMS to keep VMS alive but I was more meaning exploring visual studio as a development platform to assist in the modernization of VMS code development as another possible platform. There's a lot of love out there for visual studio

The point being made (probably poorly by myself) was that perhaps looking at how one can bring OpenVMS software development under the visual studio banner might be worth looking into? 

I've watched the promo video's for ecube systems and the development framework they provide and it's very good and what is evident from the interviewing they did was that the biggest challenge was in fact bringing the VMS programmers up to speed on modern IDE's / frameworks, in this regard, I think visual studio is easier to work with than eclipse but I am not a coder by profession, I merely have dabbled with both ide's and found visual studio by far the easiest to understand and use and the most polished in terms of code assistance and total integration

Would it be easier to have .net deployed on VMS and then use this to extend the .net platform to embrace VMS goodness, especially as the .net stack becomes open sourced under the mit open source offering? 
I don't know

Will moving VMS software development under a visual studio banner win the day for VMS? No, I don't think so but it might help and it might attract some new people out there and get them across and coding on the VMS platform. VSI cannot do it all, if we are sitting there waiting for VSI to save VMS then I fear VMS is dead already, it's going to take a community to save VMS, not just a company

Would I spend my own money on moving VMS development to visual studio if I already had an environment under the eclipse banner? No, probably not, but one can always ask for more options and that is what I was doing :-)  

Maybe eclipse is the better way in terms of gaining access to open source code, I don't know but I merely put forward a suggestion for visual studio to be looked at as a possible development ide