Re: You finally beat me down

I'm glad its working out for you Jeff. Codegear is a great company and I admit to venting a bit on the forums but when it's Friday night going into Saturday morning you can understand my frustration. This isn't the first time i've been in component upgrade hell. BCB6 made things even worse, i'd get linker errors, missing bpi references, etc. Whether its the component authors fault or not, why is this such a complicated process?

They are clearly making the effort to improve things. If I didn't give a crap, I would have just left without saying anything. I'll come back in a year and see how they are doing. I'm having a fluke problem with my components that the author cannot reproduce.

Jeff wrote:
Too all:

I have spent a number of years developing a certain app ... it uses MySQL 3.23 and Zeos 5.xx components, Turbopower OnGuard, APro, Systools, and Quickreports 3.51 all on delphi v6 pro. The years were passing by and all the components and database engine were getting older... so I decided to update...

In one swoop I changed over to BDS 2006, MySQL 4.1, Zeos 6.6.1, all turbopower stuff again, QuickReports 4.06, added XP scheme and with few few problems to conquer and it all still works too... except a few small quickreports things I am working on. Upgraded everything in a few days. I am relieved that it wasn't as hard as I thought it was going to be... with minimal help from the groups here :-) I had to edit some forms in text mode to make the zeos database switch work.

I ain't beat down... I am beat UP! (but i mean that in a good way...hehe)

Jeff



"Mike Margerum" <junk@xxxxxxxx> wrote in message news:45eaedcd$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Been using Borland products since turbo pascal... yadda yadda....

I feel like such a schmuck "upgrading" to BDS2006. I had a perfectly great BCB6 setup but I figured i'd support CodeGear and buy BDS 2006. I didn't have any immediate need to move to BDS but I was coaxed by the ide enhancements, Rave bundle, Debugger improvements, and XP theme support. 10 hours and 2 installs later, i'm still not up and running. I have crashed at least 10 times in the last 10 hours. How in god's name can installing components crash the IDE? I had to kill it from the task manager. Yes i installed update 2. In the end, this bogus package management crap did me in.

I have 2 gigs of ram and this thing is an absolute pig.

I am so frustrated to see this company blow it.

The pascal language is has remained basically unchanged since Delphi 3. Curiously this is about the time Anders left.

Your stock VCL controls lack the most basic functionality. I know you don't want to tick off your 3rd party vendors but my god man you haven't touched them in 5 years. How bout a grid control with some basic editors? You know it's bad when .net WinForms has a richer control set than you. It's having to migrate all of these 3rd party controls to the next version of the ide that keep people from upgrading.

You don't support a big chunk of the boost library. There isn't a C++ programmer worth his salt that doesn't use this library.

The whole package management thing is a disgrace. I'll die a happy man if i never need to get Indy working in BCB6 again. You did improve things in BDS 2006 by allowing for the pascal compiler to generate the C++ stuff but it crashes.

While you were wasting your time chasing .net, you could have made your flagship *native* compiler cross compile to linux, Windows CE, mac. You could have added unicode, 64 bit. Here's a tip. Nobody is going to buy BDS to do .net programming. Windows CE is begging for a delphi class native tool.

I'm moving all my future projects to .net/C#/visual studio 2005. I have used that IDE for 18 months and it has never crashed. If I have a large native app to build, it will be in WTL/wxWidgets or QT.

I'll keep BCB6 around for some quick and dirty native apps.

Good Luck guys. You are going to need it.




.

Relevant Pages

  • Re: You finally beat me down
    ... I have spent a number of years developing a certain app ... ... installing components crash the IDE? ... Your stock VCL controls lack the most basic functionality. ... native app to build, it will be in WTL/wxWidgets or QT. ...
    (borland.public.delphi.non-technical)
  • You finally beat me down
    ... I had a perfectly great BCB6 setup but I figured i'd support CodeGear and buy BDS 2006. ... I didn't have any immediate need to move to BDS but I was coaxed by the ide enhancements, Rave bundle, Debugger improvements, and XP theme support. ... It's having to migrate all of these 3rd party controls to the next version of the ide that keep people from upgrading. ... If I have a large native app to build, it will be in WTL/wxWidgets or QT. ...
    (borland.public.delphi.non-technical)
  • Re: Native Delphi IDE
    ... I think their current strategy to have an IDE which hosts both Win32 ... comparison to what us Delphi developers are used to, ... And of course, BDS ...
    (borland.public.delphi.non-technical)
  • Re: You finally beat me down
    ... expect the IDE to 'solve' that. ... BDS 2006 C++ personality. ... ask your component vendor to make support for it. ... flagship *native* compiler cross compile to linux, Windows CE, mac. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi in the enterprise
    ... Currently their view, as was stated to us by Boz, is that most of the larger customers are going to buy VS no matter what and so Borland will sell the rest of the package to them. ... As we all know, once developers get attached to a certain IDE, it's almost impossible to pry it away from them. ... If I were a salesperson the last thing I would do is try to push BDS in favor of VS.NET, when CoreSDP for .NET can be positioned as an upsell for VS.NET. ... response to a market trend where they see larger enterprises no longer buying development tools by themselves - IDEs are a *necessary but insufficient* component and are beginning to be taken for granted, and thus they are something that is included with the larger package of tools rather than independently marketed. ...
    (borland.public.delphi.non-technical)