Why is it so great to have full RAD Studio instead of just Delphi? You get more choices of languages, platforms and technologies so you can deliver more options to your customers and users. We're scheduling a webinar next month that goes into more depth on how to use the tools together, like creating a DataSnap server with Delphi or C++Builder and then having the choice to create client apps in native Windows with Delphi or C++Builder, .NET with Delphi Prism, or web-based clients with RadPHP.
8 comments:
Not so great for me, I down graded frome RAD Studio 2007 Pro to Delphi XE because I couldn't afford the price of the full Studio upgrade. I guess I've learned, no early adoption in the future, it doesn't pay.
Hey anonymous, that's the question I think a lot of people ask themselves about this offer. If you don't decide to stay at the RAD Studio level for your next upgrade what happens?
I think that scenario should be properly explained as part of this offer.
We also "downgraded" from RAD Studio 2007 to Delphi 2010.
For our C++ need we were forced to move to VC++, because BC++ dosn't build drivers, and dosn't build 64 bit applications. Moreover nowadays most libraries supports VC++ and not BC++ anymore. We bough code from an external supplier, and it was clear it was easier to build VC++ than spending the time to port it to BC++, if it was possible.
Same as well for .NET needs. Better to use C# than Delphi Prism.
And I am afraid the reasons behind this offer are exactly this trend - only Delphi still sells, the rest are tools that have hard times finding a market.
BC++ needs to be greatly improved to be able to return a competitor of VC++ and even GCC. Delphi Prism is a tool useful only to Delphi developer who don't want to learn C#. Instead of special offers, it's better they get back to deliver good tools. You can deceive a customer with a special offer once.
I upgraded from RAD Studio 2007 to XE Pro 2 months ago because I couldn't afford the RAD XE upgrade.
"Unhappy customer" doesn't begin to cover it.
g.
Uh, same here. I bought Delphi because I couldn't afford Studio.
Existing customers may suck it.
It´s sad that the ones who kept loyal and helped to support the product after so many mistakes in Delphi history don´t receive anything in return. Like many others, I purchased Delphi XE because I could not afford RAD. Where is the loyalty to the ones that supported the company?
Frankly, I have gotten bored of the whole "when is Delphi ready for 64 bit" discussion. I recently have been working with my Visual Studio 2008 (since I need some parts of code in 64bit and C++) and it's not bad. The wait has become so long (I remember discussing this in the office back in 2005) that I now can care less about the XE2 64 bit release. When the trial comes out, I will download it, try it for a month, and probably not buy it just like I have done with 2009, 2010, and XE. Frankly, they waited too long. I feel the "Buzz" will be lost on the day it comes out.
I just received a special offer to buy RAD Studio XE for the same price as Delphi Studio XE - popped it into my basket and was just about to check out when I noticed they added an optional "Service and Support". So, I know that Delphi XE has some bugs because I've already encountered them in the "trial" version I've got. Do I have to pay a yearly subscription to be able to get fixes to bugs? Seriously?
I decided not to go for the "special offer". I'll continue to use Delphi 7, because I only need it to write Win32 apps, and I've got all the updates that it has. The only component I'm missing is TTrayIcon, but there are plenty other implementations available.
It saddens me that Delphi is still 6+ years behind in the 64 bit game. To think that Intel released the 64 bit instruction set came out 12 years ago.
I too have lost a lot of respect for Borland/Inprise/Embarcadero. I've been a Pascal lover for over 20 years and it's depressing to see that a large portion of that is progress in the wrong direction.
Post a Comment