November 10, 2008
Tim Anderson on Delphi .NET Saga
Tim Anderson has a very interesting blog post with a summary of the history of Delphi for .NET, from Delphi 8 to the coming Delphi Prism. He described the U-turn from "we do the IDE" to "let's use Visual Studio", and the second U-turn from "VCL.NET only" to "use WinForms". But overall, despite errors in the past, he praises Prism and its Mono support. I think that after some mistakes there is now a viable strategy, and that this is not a resource drain for the Delphi R&D team. So it seems a win on both counts. However, we still have to see the product to be able to judge. And to figure out if this product makes sense to the developers, and how many people will actually buy it.
The problems with past version was, as Anderson puts it, "Borland released Delphi 8... Nobody wanted it." Now he specifically points out Cocoa support in Visual Studio as something specific that Microsoft won't probably support, at least not too openly. But is Mono so attractive that supporting it will get developers to Prism? This is not easy to tell...
4 Comments
Tim Anderson on Delphi .NET Saga
For multiplatform development i would love to see Delphi application running on Smartphone (Windows Mobile 5/6?)... Mono? nah...(to slow for us) Java? write once DEBUG everywhere... (no thanks, although i have success with some apps) That would be better if Codegear revive Kylix product line if we want to develop on Linux, especially if the Next Delphi (20xx) support cross compilation like "Cross Kylix" already did (but much better) I really interest on how far Lazarus and Freepascal (write once COMPILE everywhere) can support multiplatform application development, especially Win CE compiler :D http://www.lazarus.freepascal.org/Comment by Deli Soetiawan on November 11, 03:53
Tim Anderson on Delphi .NET Saga
"Borland released Delphi 8... Nobody wanted it." Who wanted Delphi Prism?Comment by Pablo Reyes on November 11, 10:44
Tim Anderson on Delphi .NET Saga
I DID want Delphi 8, that's why I bought it! It was unusable, that's all there was to it. I didn't buy any upgrades anymore until D2007. Cross-platform development: use the native toolset for each platform. Cross-platform tools either shield the user strongly, preventing effective use of the features native to each platform, or they adapt so much to each platform that only the syntax (Pascal in our case) remains familiar. As soon as you have Delphi as a VS plug-in, it will allow side-by-side comparison to C# and people will notice how much better C# is integrated into the IDE.Comment by Ken Knopfli on November 11, 11:34
Post Your Comment
Click here for posting your feedback to this blog.
There are currently 0 pending (unapproved) messages.





Tim Anderson on Delphi .NET Saga
Comment by Luigi D. Sandon on November 10, 18:51