comp.lang.ada
 help / color / mirror / Atom feed
From: Michael Dodas <miked@utw.com>
Subject: Re: M$ to STRIKE again...
Date: 1997/04/08
Date: 1997-04-08T00:00:00+00:00	[thread overview]
Message-ID: <334A78D5.49D4@utw.com> (raw)
In-Reply-To: 334969D5.4A2A@cris.com


.James Giles wrote:
.> 
.> Catherine Rees Lay wrote:
.> 
.> [...]
.> 
.> > Don't be too hard on Delphi, btw - just because Borland are
prepared .to
.> > acknowledge their bugs doesn't mean they have any more than other
.> > companies/products. The existence of a well-defined bugs list is a
.plus,
.> > not a minus.
.> 
.> It used to be (in the good old days) that all computer vendors
.(software
.> or hardware) were very up-front about errors.  They would bend over
.> backwards trying to educate users about the present buglist and the
.> status of the respective fixes.  The problem in those days was
.> complacent users who couldn't be bothered to look through the known
.bugs
.> until they got bitten.
.> 
.> These days (especially after the Intel floating-point fiasco) vendors
.> seem to be shy about even admitting to having bugs.  I suspect it's
.> really due to a perceived changed among company marketing strategists
.of
.> the expertise of the user community.  In the old days, users were
only
.> the elite professional type and would not have stood for
stone-walling
.> from the vendors.  Now, most users are naive newcomers that might shy
.> away from any company with admitted bugs - and who can be bullied
into
.> thinking any problems encountered are their own fault.  (Note: I'm
not
.> saying that this is so.  I just think that's the opinion among the
.> vendors.)  So, most companies believe it's now in their interest to
.> conceal errors if possible.
.> 
.> --
.> J. Giles
.> Ricercar Software


I agree completely with you, James.  The bugs, errors and problems that
are distributed with many of the PC software products are totally
unacceptable.  The two major reasons I see this happening is (1) to get
that next release out, not matter what, because the competition has it
and (2) more time is spent making the GUI look nice (dancing ICONS,
etc.) at the expense of the internal processes.  If you feel like that
you, as the customer, are being used as a guinea pig by your software
provider because of all of the problems, you probably are.  A lot of
people accept this.  A lot of people also take it for face value that a
software product is good just because it has company XYZ's name on it.

I don't agree with Caterine when she stated that "just because Borland
is prepared to acknowledge their bugs doesn't mean they have any more
than other companies/products".  All software is not created equally and
all software does not have as many bugs as everyone else's.  I'm not
singling out Borland on this issue--just generalizing this problem as a
whole.

If software vendors distributed mainframe software with the problems
that much of the PC vendors have, they would go out of business.  The
mainframe environments have never tolerated software with problems like
that.  Yes, mainframe software can have some problems.  But never to the
extent of what I've seen on other platforms.  Large, commercial
environment cannot afford those problems and down-time.

There are good PC software products if you take the time to find them. 
The PC tools I use for software development have proven to be very
reliable. But, just like mainframe software, I scrutinize PC software
just as much.  And, I have never been shy telling a vendor (mainframe or
PC) what I think.  Too many people forget that its YOUR dime and THEY
want it.  I do not have the time to continuously fight the same old
problems over and over.  And I've seen the same problems over and over,
from release-to-release, pop up in software.  How much of this are you
willing to accept before it causes you problems with your projects and
how your company runs?  Is the hype from software vendors worth the
gamble and your time?

Mike Dodas




  reply	other threads:[~1997-04-08  0:00 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-06  0:00 M$ to STRIKE again essoft
     [not found] ` <3348FC2E.A8B@csolve.net>
1997-04-07  0:00   ` Catherine Rees Lay
1997-04-07  0:00     ` James Giles
1997-04-08  0:00       ` Michael Dodas [this message]
1997-04-07  0:00   ` Robert Dewar
1997-04-07  0:00     ` essoft
1997-04-08  0:00       ` Peter Seebach
1997-04-07  0:00 ` Steve Lionel
1997-04-07  0:00 ` Mark Wilden
1997-04-12  0:00   ` Nick Roberts
1997-04-13  0:00     ` Bruce Rosner
1997-04-14  0:00       ` Deutscher
     [not found]         ` <3353A5E4.2FD4@sni.de>
1997-04-16  0:00           ` Tom Wheeley
1997-04-13  0:00   ` Dave Sharp
1997-04-16  0:00   ` Avi Cohen Stuart
     [not found]   ` <33555E64.2556@student.csi.cuny.edu>
1997-04-17  0:00     ` Best way to kill Microsoft (Re: M$ to STRIKE again...) William Frye
1997-04-17  0:00       ` Lint-like program for C++ Steve Dimig
1997-04-17  0:00         ` Uwe Baemayr
1997-04-18  0:00         ` Chris Durand
1997-04-18  0:00         ` Oliver Boehm
1997-04-18  0:00           ` Robert Dewar
1997-04-21  0:00           ` James Youngman
1997-04-17  0:00   ` Best way to kill Microsoft (Re: M$ to STRIKE again...) Corey Minyard
1997-04-18  0:00     ` S. Narasimh Reddy
1997-04-17  0:00       ` Da Borg
1997-04-18  0:00         ` Jay Lyerly
1997-04-18  0:00         ` Emilio Lopes
1997-04-18  0:00           ` M A
1997-04-18  0:00             ` Da Borg
1997-04-20  0:00               ` Robert Dewar
1997-04-18  0:00             ` Jose Miguel Perez
1997-04-21  0:00             ` Paul Oldham
1997-04-21  0:00               ` C.Pitz
1997-04-18  0:00       ` Alexander Lehmann
1997-04-18  0:00         ` kwm
1997-04-18  0:00     ` Kim Robert Blix
1997-04-18  0:00   ` Corey Minyard
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox