Your reviewer was looking at Delphi Roadmap and community responses[1] and decided to write the real Delphi roadmap:
Official Roadmap can be found here:
http://edn.embarcadero.com/article/39934
Your reviewer thinks this Delphi Roadmap reflects the current situation:
Pack more and more useless features into Delphi and then later, depreciate or don't release fixes for them.
- Nearly every new feature that has came into Delphi, is half-baked, or half-done, from ill-fated ReportSmith, BDE, Bold for Delphi, NET10, NET11, IBX, DBExpress[4]
- Think about BDE, how FoxPro 2.6 support was never properly handled or how Oracle 9i support for BCD numbers is half-supported, or how IBX components do not have transactions. Or how Midas, a promising technology is no longer relevant. Docking is still rubbish[2], or very limited undo/redo[3].
The only "suggested" reason why DelphiX or Delphi64 is taking so long to come out, is they need to "update" all those depreciated codes. Think about it...
Unicode - half-implemented and additional 3rd party issues
Your reviewer found out none of the Delphi RTL (Run-Time Library) supports an important aspect of Unicode - Composites, Ligatures and Surrogate Points. Even worse, none of the 3rd party component vendors support Composites, Ligatures and Surrogate correctly.
For 3rd party vendors, they need to "buy" latest version of Delphi and then update the libraries. Some vendors have no good Delphi 2009 implementation (probably because they are out-of-business).
Release half-implementations and full-implemenations sold separately.
Your reviewer wonders what kind of component technology is inside Delphi, since everything useful is sold separately. For example, to get full license of IntraWeb, you need to buy it, to get fully working MySQL support, you need to buy 3rd party. Go figure. If it costs US$2500+ to buy Delphi and another few thousand license here, how much costs will eat-up profits?
When the community ask for fully-working implementation, Embarcadero's response is that they don't compete with 3rd party vendors. Maybe if Embarcadero did things right in first place, there would not be this annoying 3rd party vendor with "correct implementation" and Embarcadero's half-working solution...
Make each Delphi version as unpleasant to use as possible
Your reviewer thinks very few people buy Delphi, since all those crazy bugs were fixed only in Delphi 2010 update 3/4 and 4/5. (Forget about buying Delphi 2006, 2007, 2009 - these versions were only to bring in money)
Your reviewer looked at one particular interesting bug:
http://blogs.embarcadero.com/nickhodges/2009/12/14/39338 (comment #29,#30,#31)
and wondered if DelphiHater was the 2nd person (but kept quiet) to discover this bug many months ago. Why is it not fixed? - probably because nobody uses this feature ;)
With Delphi 2009/2010, you had to upgrade all your libraries, all your codes, and there are so many hidden costs to upgrade "everything" to use Delphi 2009/Delphi 2010. With so much costs, it's no wonder it's hard to "upgrade" to Delphi 2009/2010...
Delphi forever - Sorry, you lost your job, your house got forclosed, your car got repossessed
Your reviewer thinks using Delphi is like being proud and totally arrogant. There are few jobs, expensive costs, and sooner or later, don't be surprised you'll be like the Delphi Bistro person - it's time to move on.[5]
Delphi 64-bit - Keep promising but don't deliver
After DelphiX, there's Chromium, but that could be in year 2011, if timelines keep slipping, maybe, just think... there is no Delphi 64-bits, it does not exist. End of story, We've waited since nearly 4 years for this (since Delphi 2006). Everything else is empty promises. Think about it., another year will pass, another year will pass, and still no Delphi 64-bits...
Use TeamB to keep customers entertained...
What purpose is it for TeamB to keep replying to non-technical, and off-topic for except perhaps to keep customers entertained with snappy replies?
Make each Delphi version more and more expensive
What purpose is it to charge SA (Software Assurance), then increase prices, and then remove free-versions of Delphi, except to make customers pay and pay? The newer people cannot get licenses without paying lots of money, the older customers hate to pay and pay for what seems like "bug fixes"... Did I mention about the 20%-30% increase in SA price this year?
Make Delphi call home, make Delphi copy-protection more and more stronger...
Your reviewer sees with each version, each release, the copy-protection has gotten lot more stronger and stronger. Your reviewer wonders why Embarcadero focuses on copy-protection part and not legal enforcement part? ... Your reviewer would love for more of his friends to get sued or asked to pay-up 10 times the cost of Delphi itself (US$20,000)... :)
Conclusions
This is the Unofficial "Delphi" roadmap, think about it, it feels more like the truth than the official Roadmap :)
1] https://forums.embarcadero.com/thread.jspa?messageID=207459
2] Docking still Rubbish - https://forums.embarcadero.com/thread.jspa?messageID=207362
3] Limited Undo/redo - https://forums.embarcadero.com/thread.jspa?messageID=207388&tstart=0#207388
4] Dr. Bob "discovers" Datasnap 2010 security is nonexistent - http://www.sandon.it/?q=node/52
5] No Delphi Jobs - http://delphibistro.com/?p=49
Official Roadmap can be found here:
http://edn.embarcadero.com/article/39934
Your reviewer thinks this Delphi Roadmap reflects the current situation:
Pack more and more useless features into Delphi and then later, depreciate or don't release fixes for them.
- Nearly every new feature that has came into Delphi, is half-baked, or half-done, from ill-fated ReportSmith, BDE, Bold for Delphi, NET10, NET11, IBX, DBExpress[4]
- Think about BDE, how FoxPro 2.6 support was never properly handled or how Oracle 9i support for BCD numbers is half-supported, or how IBX components do not have transactions. Or how Midas, a promising technology is no longer relevant. Docking is still rubbish[2], or very limited undo/redo[3].
The only "suggested" reason why DelphiX or Delphi64 is taking so long to come out, is they need to "update" all those depreciated codes. Think about it...
Unicode - half-implemented and additional 3rd party issues
Your reviewer found out none of the Delphi RTL (Run-Time Library) supports an important aspect of Unicode - Composites, Ligatures and Surrogate Points. Even worse, none of the 3rd party component vendors support Composites, Ligatures and Surrogate correctly.
For 3rd party vendors, they need to "buy" latest version of Delphi and then update the libraries. Some vendors have no good Delphi 2009 implementation (probably because they are out-of-business).
Release half-implementations and full-implemenations sold separately.
Your reviewer wonders what kind of component technology is inside Delphi, since everything useful is sold separately. For example, to get full license of IntraWeb, you need to buy it, to get fully working MySQL support, you need to buy 3rd party. Go figure. If it costs US$2500+ to buy Delphi and another few thousand license here, how much costs will eat-up profits?
When the community ask for fully-working implementation, Embarcadero's response is that they don't compete with 3rd party vendors. Maybe if Embarcadero did things right in first place, there would not be this annoying 3rd party vendor with "correct implementation" and Embarcadero's half-working solution...
Make each Delphi version as unpleasant to use as possible
Your reviewer thinks very few people buy Delphi, since all those crazy bugs were fixed only in Delphi 2010 update 3/4 and 4/5. (Forget about buying Delphi 2006, 2007, 2009 - these versions were only to bring in money)
Your reviewer looked at one particular interesting bug:
http://blogs.embarcadero.com/nickhodges/2009/12/14/39338 (comment #29,#30,#31)
and wondered if DelphiHater was the 2nd person (but kept quiet) to discover this bug many months ago. Why is it not fixed? - probably because nobody uses this feature ;)
With Delphi 2009/2010, you had to upgrade all your libraries, all your codes, and there are so many hidden costs to upgrade "everything" to use Delphi 2009/Delphi 2010. With so much costs, it's no wonder it's hard to "upgrade" to Delphi 2009/2010...
Delphi forever - Sorry, you lost your job, your house got forclosed, your car got repossessed
Your reviewer thinks using Delphi is like being proud and totally arrogant. There are few jobs, expensive costs, and sooner or later, don't be surprised you'll be like the Delphi Bistro person - it's time to move on.[5]
Delphi 64-bit - Keep promising but don't deliver
After DelphiX, there's Chromium, but that could be in year 2011, if timelines keep slipping, maybe, just think... there is no Delphi 64-bits, it does not exist. End of story, We've waited since nearly 4 years for this (since Delphi 2006). Everything else is empty promises. Think about it., another year will pass, another year will pass, and still no Delphi 64-bits...
Use TeamB to keep customers entertained...
What purpose is it for TeamB to keep replying to non-technical, and off-topic for except perhaps to keep customers entertained with snappy replies?
Make each Delphi version more and more expensive
What purpose is it to charge SA (Software Assurance), then increase prices, and then remove free-versions of Delphi, except to make customers pay and pay? The newer people cannot get licenses without paying lots of money, the older customers hate to pay and pay for what seems like "bug fixes"... Did I mention about the 20%-30% increase in SA price this year?
Make Delphi call home, make Delphi copy-protection more and more stronger...
Your reviewer sees with each version, each release, the copy-protection has gotten lot more stronger and stronger. Your reviewer wonders why Embarcadero focuses on copy-protection part and not legal enforcement part? ... Your reviewer would love for more of his friends to get sued or asked to pay-up 10 times the cost of Delphi itself (US$20,000)... :)
Conclusions
This is the Unofficial "Delphi" roadmap, think about it, it feels more like the truth than the official Roadmap :)
1] https://forums.embarcadero.com/thread.jspa?messageID=207459
2] Docking still Rubbish - https://forums.embarcadero.com/thread.jspa?messageID=207362
3] Limited Undo/redo - https://forums.embarcadero.com/thread.jspa?messageID=207388&tstart=0#207388
4] Dr. Bob "discovers" Datasnap 2010 security is nonexistent - http://www.sandon.it/?q=node/52
5] No Delphi Jobs - http://delphibistro.com/?p=49
3 comments:
100% agree. I pray for a stable Delphi version.
Since years we must pay for beta products. There are much much much more bugs as features.
I have never seen another software product that have so many expenses and is overloaded with uncountable bugs.
I love and hate Delphi also. The hate is for the bugs, we must pay for.
I use Delphi since version 1. Currently using Delphi 2009. I generally like it but the technology is old. Glad Unicode was finally delivered. What I need is support for mobile platforms (think about millions of phones!) and 64-bit (for shell extensions). Gestures may be good in the future but not now, since there is no mobile platform support anyway. How many need gestures on PC platform now? It all sounds nice for marketing, though. I'll not upgrade before I get 64-bit support.
Fri 4/02/2010 11:53 am. I stopped at Delphi version 7, 2002 or so. I want to point out that many of your totally legitimate complaints would be a heck of a lot less annoying if Delphi were *cheaper* -- i.e., like it used to be. One expects an inexpensive product to not support various "edge" things like MySQL etc. and force you to buy 3rd-party products -- the excuse, and a fair one, is that supporting these things correctly in the main product makes all users pay for features only a few use.
But when the stupid thing -- well I used to joke about the "Insane Millionaire Version" of Delphi, back in the day when the "pro" version was a mere $300. But now *every* version is the Insane Millionaire Version!
Obviously I don't have to use Delphi to make a living. But I'm still very fond of it, and it's *still* the easiest way to write Windows GUI programs. Apparently nobody wanted to do that!
======================================
j.g. owen * email: owen_bda4@yahoo.com
web: http://owenlabs.org
======================================
Post a Comment