Borland only offered one Service Pack, leaving several bugs behind that they knew about. NET, Delphi will work 15% of the time with the same code. Even simple Win API programming which work perfectly in VB6 and. Something simple like an FTP client, couldn't stay working. Writing an app using a version of Delphi a couple versions back just couldn't work. However, I, like many others, outgrew it over 10 years ago.
I suspect a lot of those sales are simply coming from companies switching away from other failures in that space. I understand that they have increased sales, but increasing sales in a shrinking marketplace isn't exactly where they need to be. Unless Embarcadero changes direction, Delphi will continue to be a Desktop only product and it's potential market share will continue to shrink. Either too little too late or simply bad execution, I'm not sure. Yes, Borland screwed up, royally, but the main problem was that they didn't embrace the web.Net and Java did and won the hearts and minds of the vast majority of the development staff. To be sure, there were new Desktop applications being built, but quite frankly the mainstream had moved on.
Corporate was moving to the web and embracing those languages. Around this time most compiler companies started failing. By D7, a new application was more likely to be run in a browser than on the desktop. By D4 companies were basically testing the waters with Internet development. When D1 came out in ('94?) there were only two development choices: Desktop or Server. One aspect that a lot people have either ignored or somehow missed: Delphi failed to stay relevant.
BORLAND DEVELOPER STUDIO 2006 WINDOWS
With support for 64-bit Windows AND OSX and iOS platforms (iOS support is due to FPC), it is the first Delphi release I have been excited about in quite some time. I am really looking forward to the upcoming Delphi XE2.
BORLAND DEVELOPER STUDIO 2006 FREE
I eventually gave up waiting on a 64-bit version of the compiler from CodeGear, and ported our company's calculation engine to the Free Pascal Compiler (FPC) so that we now support the 64-bit Windows as well as 32/64-bit Linux platforms. Later on, it was widely known that Borland was attempting to sell Delphi to an outside company, which never inspires confidence in your users.Īfter CodeGear acquired it, I think that the lack of a 64-bit compiler may have hampered it's adoption. What has caused Delphi's decline over time? I think that many of the posts have covered several of the facets involved: Borland ne' Inprise ne' Borland's loss of focus on their core supporters. It was at this time that we switched from VB to 100% Delphi. When it came time to move from 16 to 32-bits, our development team took the opportunity to change the architecture of our product and separate the UI from the calculation engine. At the time, we were using Visual Basic 3 for most of our Windows development, and I found that Delphi was head and shoulders above VB 3 for our needs. I have used Delphi since Version 1, and introduced it to my workplace. It's "Embarcadero Delphi" now, and it's very much alive and kicking. Despite both the recession and Delphi being a commercial-only tool in a perceived "age of open-source development," sales have been really strong and the team's been able to make a lot of progress. They've put a lot of work and effort into it, and the product quality has improved tremendously in the last few releases. Borland no longer exists.Įmbarcadero, though, actually cares about Delphi. Within a few months of the sale, Borland stock fell below $1/share and they were bought out by a "corporate graveyard" company that basically does nothing but manage licensing fees on existing products. Now their big claim to fame is that they're the guys who make Delphi.
Borland sold their entire development tools division to Embarcadero Technologies, which up to that point was mostly known for database-related software. I even heard from some former Borland employees at the Delphi Live! conference a few years ago that their sales people were actively discouraged and dis-incentivized (is that a word?) from trying to sell Delphi at all, even to potential clients who expressed interest up-front.Ī few years back, things changed. So they put a lot of resources into developing and promoting that instead of Delphi, and let the development tools branch languish. They had a really large product line, and the main thing that people were interested in was Delphi, but what the PHBs thought was going to be big was not their development tools, but their Application Lifecycle Management tools. Delphi is still around and very much alive, but under new ownership.īorland really lost their way.
0 kommentar(er)
