Board index » delphi » Re: The Borland Vision: Wrong?

2003-11-10 12:56:09 PM
delphi220
"Alessandro Federici" <XXXX@XXXXX.COM>
choose a different approach. Unfortunately, that is the insidious nature of
many of the bugs that can be 'solved' using workarounds. The showstoppers
are actually the easiest to deal with as you are forced to make a decision.
Take it or leave it. It is the 'minor problems' that can accumulate without
you realising it until you are in so deep that it is as expensive to back
out as it is to proceed.
Chris Burrows
CFB Software
www.cfbsoftware.com
 

"Steve Tyrakowski" <XXXX@XXXXX.COM>writes
had Software Maintenance contracts which clearly specified minimum service
expectations. Software defects can be categorised in terms of severity and
impact on the customer, and expected response times can be associated with
these levels. I have always had the view that serious defect correction
takes priority over enhancement work.
On a related issue, does anyone know what is in the 'fine print' of the
Software Assurance terms and conditions? From the blurb I have seen, the
only guarantee of any deliverables in any 12 month period is three support
phone calls.
Chris Burrows
CFB Software
www.cfbsoftware.com
 

Lauchlan M writes:
Christopher Latta
 

"Steve Tyrakowski" <XXXX@XXXXX.COM>writes
This just adds to the many alternatives we have to conti use using Delphi
and go around issues.
 

"Chris Burrows" <XXXX@XXXXX.COM>writes
It doesn't just happen in one day!!
to address (or find a solution for) in other people's products I look for
alternatives. 2 hours would already be too expensive for my taste.
All that without even considering the fact that before using something I
spend a considerable amount of time ensuring the tool is good but that's
another topic and we already talked about that.
What goes around comes around: test carefully a product before jumping into
final development...
 

"Alessandro Federici" <XXXX@XXXXX.COM>writes
 

 

Which isn't a problem with me. But he still didn't answer my question.
How do we get Borland to give us timely SPs?
Andrew Rybenkov writes:
Thomas Miller
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork
www.bss-software.com
sourceforge.net/projects/dbexpressplus
 

Well with any Borland product you buy from here on out, it is not
a given. That is my problem. I am trying to decide on whether
our company should jump ship and if so, to what. Should I continue
time on dbExpressPlus or Lazarus? Should I go to C#? The most
cost effective option is to get Borland to do the right thing
and release some SP for D7. The question is how do we force them
to do so? Is a lawsuit the only way to get Borland to do the
right thing?
Lauchlan M writes:
Thomas Miller
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork
www.bss-software.com
sourceforge.net/projects/bexpressplus
 

"Ronald McDonald" <XXXX@XXXXX.COM>writes:
But personally I think It should consider
a long term aim.
I have sometimes deal with companies that still
run win3.X and even DOS programs !!!
And they are not interested or have the resources
to migrate...
I consider ".net" more like a OS change,
such as the migration from "DOS" to "win3.X"
and "win3.X" to "win95+".
I think is good that Borland prepare as soon
as possible to work with ".net".
But Im also worried that Borland
drops too soon support and updates
for Win32.
Many companies are not interested
in upgrade its software tools.
I personally became fired
because my employer drop Delphi
programming and replaced by a
weird mixture of Java,
C++ and not so common programming
enviroments !!!
I also remember about 10 years ago,
how many programmers complain
because Borland didnt release
Turbo Pascal for DOS 8.
It wasnt that all those programers
didnt realized that Windows programming
was the next step, as it does with ".net"
now.
Many of them just need to continue supporting
the existing DOS enviroment for many years,
even that they wanted GUIs...
History repeats itself...
MS is "encouraging" developers and companies
to take ".net" as the next step.
Let's see where is taken us...
 

Otherwise it is FUD.
individuals.
Ed Dressel
 

relations with Borland, be a little cheaper, and be a more positive
engagement. And you can set one up on a website somewhere and direct people
to it whenever they raise bug/support issues.
If you did that, you could collect, as well as a digital 'signature'
(actually just customer/developer name would do), specific comments about
what people are concerned about and eventually ship these all off together
to Borland at once.
If Borland had a petition from as little as 100 developers it would be
noted, 500 or 1000 developers it would be quite significant, from 5,000
devleopers or more would be very hard to ignore.
But if you do it, be very clear about the kind of outcome you want. ie,
specifically request explicit targets/commitments such as
- all bug reports opened and assigned an action within (some period, eg 2
weeks),
- some high percentage (say 90%) of bug reports that are assigned an action
by Borland to be fixed/resolved within some period (eg 1 month from the
action commencing) and the other 10% within six months (recognising that
some bug fixes would take longer or may impact on the rest of the program
and QA more severely)
- all fixes to be shipped in service packs within some given period (eg
within a quarterly period) from the date of the fix being developed.
or whatever you think appropriate.
Lauchlan M
 

On 10-Nov-03, coyotebuddy said:
--
Bill
--------
"We may become the first society destroyed by its own experts --
especially experts in fields where there is no expertise that can be
verified by facts." -- Thomas Sowell
 

 

On 10-Nov-03, Andrew Rybenkov said:
--
Bill
--------
"We may become the first society destroyed by its own experts --
especially experts in fields where there is no expertise that can be
verified by facts." -- Thomas Sowell