Amiga 3000UX, X, OpenLook, Motif, Color, A2410, Etc. (somewhat long)

Skank George L skank at iastate.edu
Sat Mar 23 19:00:26 AEST 1991


In article <1991Mar19.003209.6819 at kessner.denver.co.us> david at kessner.denver.co.us (David D. Kessner) writes:
>In article <1426 at amix.commodore.com> skrenta at amix.commodore.com (Rich Skrenta) writes:
>>Of course there's a next version!  I've never heard a developer say there's
>>not going to be another release--unless the product is dead.  Our release 2.0
>>is going to have some major improvements, including a kernel and libraries
>>built with a different compiler.  And of course we keep polishing it as we go.
>>Would you rather we held up the release for "piddly" cosmetic problems?
>
>I would not buy a system that is "stagnent"-- that is not adjusting to the 
>times.  But I wonder about a system that is as new a Amiga UNIX and yet has 
>so much talk about the next version...  It is just an indicator of the first
>versions status.

     This would bother me, but, for instance, Microsoft has the same problem.
The first releases of many Microsoft titles were buggy and didn't perform up
to developer expectations, to that end I think Commodore has far exceeded
Microsoft in how well the initial release of the software works, especially
considering the *huge* size of the project.  Microsoft (for a while at least)
started to develop a reputation for buggy initial releases, it was so bad that
the president set a company goal to improve the quality of future titles'
initial releases.  It happens to all the big companies, so why shouldn't it
happen to Commodore too?  (this is just to keep things in perspective, I
don't like unfinished software anymore than the next person)

					--George




More information about the Comp.unix.amiga mailing list