🚀 go-pugleaf

In article <1500@blake.acs.washington.edu>, a360ad@blake.acs.washington.edu (Gnurr) writes:
# In article <56208@yale-celray.yale.UUCP> fischer-michael@CS.YALE.EDU (Michael Fischer) writes:
# >In article <1439@atari.UUCP> kbad@atari.UUCP (Ken Badertscher) writes:
# >>  Unfortunately, I can't discuss the OS changes that we're making until
# >>they're releaseable.  Sorry!
#
# This seems like a bad policy for Atari to adopt.  How can you know
# what the community wants or what the implications of proposed OS
# changes might be if you don't discuss them before implementing them?
# 
# Now there's some logic for you... But... No one ever said Building computers
# Was a democratic art...

Imagine what would happen if Atari announced that they were working on a 
new multitasking version of TOS with 32 windows, built-in GDOS with outline
fonts, and unlimited desk accessories...  
The count down would start that day.  Two months later people would be 
complaining that it had been two months and still no TOS 2.0... and so on.
We've all seen it.  I know that I for one don't like it.  The policy of
keeping quiet until you _know_ that things will really materialize and you
at least have an estimate of how long it will be seems like a good one to me.

# I am not being fascist .... i mean, facetious...
# 
# -kevin


-- 
       Steve Whitney         Internet:   maverick@portia.stanford.edu
                             UUCP:      ..!decwrl!portia.stanford.edu!maverick
  "It's never really the     Bitnet:    maverick%portia.stanford.edu@stanford
       last minute!"         GEnie:     S.WHITNEY