[Info-vax] How about RdB for x86 VMS?

[Bill Gunshannon]

In article <54089b7d$0$1263$c3e8da3$b1356c67 at news.astraweb.com>,
	JF Mezei <jfmezei.spamnot at vaxination.ca> writes:
> On 14-09-04 10:09, Stephen Hoffman wrote:
> 
>> Are there questions?  Sure.  Concerns?  Definitely.  Want answers?  
>> Stop fscking around in comp.os.vms and contact VSI or the third-party 
>> vendor directly.
> 
> The discussions here won't force VSI to answer here. But they give VSI
> an idea of the types of questions/priorities that people attending may have.

That's assuming the people at VSI have the time to waste reading here.
My work is much less demanding or important as what they are getting
into and yet people here must have noticed there were times when I
became somewhat scarce in this domain.  That was because even I don't
place USENET at the top of my list of things that must be done.

> 
> In other words, by looking at comp.os.vms, VSI can prepare itself for
> every possible question that could be asked during the upcoming events
> and if they cove most of these questions then a lot of people will be
> satisfied.

Or they can just take the input being provided by paying and potential
paying customers.  Hobbyists are nice, but we aren't the ones paying
the bills.

> 
>> maps and support statements, but most end-users will want to see and 
>> feel and touch the release and the hardware (circa 2018) before you
> 
> I though x86 was to be circa 2016 ? (which would mean developpers would
> start porting mid to late 2015 based on early incomplete beta releases).

The 2018 kinf took me by surprise, too, but at this stage of the game
any estimate is more a guess than certainty.  I am willing to wait and
see how things develop.

bill

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>