| Subject | Re: [Firebird-general] Delphi Applications with Firebird |
|---|---|
| Author | Helen Borrie |
| Post date | 2008-07-24T01:11:36Z |
At 08:19 24/07/2008, you wrote:
However, I don't share your doubts about the future of OP, the language. The things we've done well with Delphi in the past are worth keeping. These days, IMO, it's essential to escape from those old, monumental applications and modularise to the nth degree. There are better ways than OP to do some things these days and modern system architectures reflect that.
As for support for old code/help with redevelopment, if you have specifics and you are willing to think beyond the old, 20th-century closed boxes of "must have people on site" and "must restrict architecture to what we were doing in 1998", then why not make use of the firebird-job-board to put a team together to address your problems?
Helen
>HiThat's impossible to say. Polls done on third-party websites only catch those who visit those websites. Typically the catchment for the Brazilian site is Delphi users so it would be surprising if the numbers there were not biased towards Delphi. Hearsay and known activity are probably at least as reliable....Jaybird, .NET/Mono and IBPP are very popular; there's a lot of pressure on the Python, PHP and ODBC sides to meet unmet demands....
>
>I was wondering if anyone knows what percentage of applications that
>use Firebird are written in Delphi?
>I ask because I think Delphi's general usage is already shrinking andI guess Embarcadero doesn't share your feelings! Although it's true that Borland has pretended for years that its "new versions" were giving you something you didn't have (or couldn't get) already, ObjectPascal is what it is - a language that is actively and well-supported with interfaces for Firebird. I'm using Delphi 7 and IBO mostly and don't have any plans to drop them.
>I feel like it is only going to continue to do so.
>If Delphi does continue to shrink I was wondering what effect that will have onDelphi is an IDE. Borland wasn't selling enough in their colourful boxes in recent years to make it a "seller". The underlying language hasn't shrunk...has it? I think the "shrink" perception has a lot to do with the uncertainty surrounding Borland products in general over the past decade. OP and IDE's for it aren't going to go away any time soon...even if FreePascal and Mono eventually end up being the spiritual home.
>Firebird's growth.
>I work on a large system with millions of lines of Delphi code so weAs a support tech, I'm aware of the kinds of problems that occur with old Delphi code that came from now-defunct companies. Before the tech-wreck, such companies were everywhere, both for components and for software whose quality was, at best, questionable. They've tended to be technological lock-ins, monumental rather than modular, and many of them are past their use-by date. I don't think you're alone in needing to confront this problem.
>need to consider where things will be in 3 to 5 years from now which
>is why I am interested. We already are having a lot of problems
>getting support for some Delphi code we have purchased from 3rd parties.
However, I don't share your doubts about the future of OP, the language. The things we've done well with Delphi in the past are worth keeping. These days, IMO, it's essential to escape from those old, monumental applications and modularise to the nth degree. There are better ways than OP to do some things these days and modern system architectures reflect that.
As for support for old code/help with redevelopment, if you have specifics and you are willing to think beyond the old, 20th-century closed boxes of "must have people on site" and "must restrict architecture to what we were doing in 1998", then why not make use of the firebird-job-board to put a team together to address your problems?
Helen