Dave,You are 100% right. As a shareholder, it pains me to think that IBM is forgetting how it got into trouble in the earlier part of this decade by ignoring customer wishes. History does tend to repeat itself. I am sure Kazakstan is not all that bad now. They even are moving their capital north by 800 miles next month! That country has so much oil, the Saudis want them to join OPEC! Maybe Dave K can put us up there :-)
Sorry for the previously empty response, I'm still adjusting to these new
"features" that AOL is providing me.
In a message dated 97-11-13 00:48:12 EST, you write:
> DAsmussen@aol.com wrote:
<<snip advert stuff>>
> > Ten years is outlined in company policy somewhere. That's many years'
> > of still unconverted S/36's it took to introduce the A/36. Probably
> > how long it takes Dave M. to get V3R3 ;-D...
> I am saving this message Dean, so you can eat crow when it happens much
Well Dave, it pains me to think that the poor phrasing of the above (_GOTTA_
get a new keyboard!) is going to be retained for the next nine years ;-)! As
I stated before on the "CISC Needs Some Consideration" thread, I'm with you
100% -- I just don't think that you stand a chance in Hades of getting what
you want from IBM in the near future. In fact, unless you've heard something
that you're not sharing with the rest of us, I'd almost be willing to fly to
Kazakstan and let you _buy_ me some crow for dinner should V3R3 happen (but I
always figured I'd starve to death in the former Soviet Republics, as I hate
beets, turnips, and most other "root" vegetables that are so popular there)!
I know that IBM's current position on CISC is wrong, you know that IBM's
current position on CISC is wrong, people that work for or through IBM but
cannot say so know that IBM's current position on CISC is wrong -- that's not
going to make V3R3 happen, though. Only when the same hordes that refused to
"upgrade" from the S/36 have proven themselves as intractable on the CISC
will IBM offer alternatives...
Dave Mahadevan.. mailto:firstname.lastname@example.org