One item in my previous post that I specifically didn't address is the notion of using Eclipse instead of VS. Again, this is something we'd be remiss to ignore. However, the primary ding against Eclipse is its reliance on a JVM. Were it not for the fact that we are trying to support the .NET platform, this might be a reasonable path to persue. I just don't see how we could create a reasonable tool that hosted not only the JVM, but also the CLR in the same process! Yes, Eclipse would be much less encumbering from a business perspective than VS, but I have to think about the developer experience. I, as a developer, would find it very hard to swallow if I had an IDE that fired up both the JVM and CLR in process.
Much of the same issues surrounding what does Eclipse give us and what we'd still have to build. In fact you can substitute Eclipse for VS in much of this post. Of course some of it doesn't apply, but you can get and idea of the scope of things involved.
Finally there is the shear fact that there is nearly 12 years invested in a lot of the current Delphi/Galileo IDE codebase. It's not perfect. It has some rough edges. However, I will point out that it was also the first IDE framework ever released by Borland that supports multiple languages out of the box. I owe a lot of this to the dedication and talent that we have and have had on the Delphi team. Now we've announced our intention of folding C++Builder into the Galileo IDE, which has only been made possible due to the work we'd been doing over the past 2-3 years.
Reduce development time and get to market faster with RAD Studio, Delphi, or C++Builder. Design. Code. Compile. Deploy.
Start Free Trial
Free Delphi Community Edition
Free C++Builder Community Edition