Omnis (Blyth) is using paying customers as beta testers !

Thread View: comp.sys.mac.databases

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Jerry Sy Sun, 02 Aug 1992 13:43

#106

Author: Jerry Sy
Date: Sun, 02 Aug 1992 13:43

18 lines
1196 bytes

I received the 1.1 beta version a week ago and guess what ?

its got 22 pages of over 200 different bugs from the previous version 
that were supposedly fixed !

that's right, over 200 bugs and that is not a typo.

geez, I certainly wouldn't want to buy a $500 program just to be a beta
tester, or buy a $500 beta program for that matter! a program with that
many bugs, to me is a beta program!


as far as I'm concerned, a $500 should not be allowed to be released with
this many bugs (even though a user may only encounter, say 10% of it).

there should be aconsumer group that checks the quality of a program,
(particularly high priced one) before it gets released.

Re: Omnis (Blyth) is using paying customers as beta testers !

#107

Author: Brent Chapman
Date: Mon, 03 Aug 1992 00:00

13 lines
935 bytes

jxs18@po.CWRU.Edu (Jerry Sy) writes:

>there should be aconsumer group that checks the quality of a program,
>(particularly high priced one) before it gets released.

And how much are you willing to pay to belong to such a consumer group?


-Brent
--
Brent Chapman                                   Great Circle Associates
Brent@GreatCircle.COM                           1057 West Dana Street
+1 415 962 0841                                 Mountain View, CA  94041

Re: Omnis (Blyth) is using paying customers as beta testers !

#114

Author: Cy Shuster
Date: Tue, 04 Aug 1992 21:52

21 lines
1425 bytes

I think it's an advantage to use a product with lots of known bugs.
It means it's been tested, for one thing, and that they've fixed
the most serious bugs.

It's making the first flight of a new aircraft that I'd be afraid
of.

It's perfectly possible to have hundreds of bugs against a product,
all of which take 25 or more steps to reproduce, or which are
sensitive only to unusual combinations of INITs. It's just not
realistic to expect bug-free software. Furthermore, you can make a
product gigantic by adding in endless error checking for brain-dead
inputs... and also send performance into the toilet, as well. I'm
sure the average person takes on many more risks driving his daily
commute (do you wear your seatbelt? Speed?).

Debugging is like giving a haircut: you fix the obvious problems, then
go around finishing things up until what you do hardly makes a
difference. 

--Cy--

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads