Hello science in TAOO [long]
b.xavier at internet.lu
Sun Oct 16 02:44:11 CDT 2005
You miss the point that one can only do so much testing and still depend
lots on the user's feedback - user or tester alike! Look at Rev's bugzilla
database and how it helps them make happy users each release.
Which is why I haven't released much other than the working stacks and not
the other 20 million features. I guess missing features are better than
non-working features ;) Then, like a famous software, new releases break old
I haven't released my spell checker because of a "couple" bugs only... And I
dont use it "that" often nor was there much demand so other more important
features warrant more attention... When that part is finished and tested and
running, I'll be releasing much more... Moires are easy, real applications
That being said, when I thought I had really removed all the bugs in the
MoireX program, TJFrame found one in 2 clicks after he started using the
> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com
> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of
> Richard Gaskin
> Sent: Sunday, October 16, 2005 9:10 AM
> To: How to use Revolution
> Subject: Re: Hello science in TAOO [long]
> MisterX wrote:
> >>I get frustrated after about 10 minutes and throw whatever it is in
> >>the trash and think that I will wait until you have it
> fixed and then
> >>look at it. Only problem is that the story never seems to change.
> > That's because "VERY VERY FEW" people will reply with the issues
> > encountered so that I can fix them on the spot! I try to
> test a maximum.
> All software always has bugs.
> That said, most useful software has so few bugs that the
> utility of the work is self-evident long before the first bug
> is encountered.
> So while it may not be cost-effective to attempt to deliver
> one of the world's few (only?) bug-free wares, at a minimum
> the developer must catch and address enough bugs themselves
> that the user will be sufficiently hooked by the work before
> they encounter the first annoyance.
> If the user encounters annoyances before the utility of the
> work is self-evident, one can harldy blame them for simply
> moving on with their busy day.
> If as the creator of the toolkit you feel folks are missing
> out by not using your tool, bugs and all, consider this:
> To the degree that your tool truly helps developers be more
> productive, you'll still be able to deploy an ever greater
> number of high-quality commercial applications with it, and
> with less competition as fewer people use it.
> Ship successful software, and users of the library that made
> that possible will follow.
> Richard Gaskin
> Managing Editor, revJournal
> Rev tips, tutorials and more: http://www.revJournal.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage
> your subscription preferences:
More information about the use-livecode