Then try to write a web server server application
using dbexpress and see how it eats all the memory
in a few days because of the memory holes.
or see how some of the basic things are not working
with databases.
Then check the QualityCentral reports back 2 years
and realize that those bugs are well known and not
fixed until today.
Plus isn't it quite frustrating that soon you will have
to work with Linux distributions not even supported
anymore or that you cannot use the latest ones because
the last version supported is 2-3 years old?
Isn't it suspicious when teamB and Borland employees
themselves say to customers in the newsgroups to
use 3rd party db drivers if Borlands' not working?
I think that people is rightfully very pissed off
how Borland handled Kylix. Why did they pay big
bucks for Kylix Enterprise if the features promised
are not even working and the found bugs not fixed?
I am personaly speaking from my own experience when
I cite examples here. But you can check all these
newsgroups for earlier posts and see that there are
a lot of people having serious problems with Kylix.
WMueller wrote:
Quote
BoBo wrote:
>What do you expect from a product with full of serious bugs and no bug
>fixes for years?
>Just check the QC bug reports for bugs going back as far as two years...
>They did not release the source for dbExpress which would have been
>fixed within days by the community. And this is just one example.
>
Was it really that serious ? I know Kylix for just four weeks now. After
a lot of Problems with trying to install it on SuSe 8.2 I decided to
follow the Borland limit of SuSe 7.3
After that, my several little experimental applications worked well, so
far. ( C++ Version with third party Oracle Access Components)
But I can not really claim to have challenged it :-))
