Leveraging Delphi and C++Builder - Mutually Beneficial
Following the Delphi 24 Hour event, and several other rumblings and sightings over the past few weeks regarding future Borland products, has given me even more certainty that C++Builder for Win32 (w/ VCL support) is well on its way back. Some of the evidence for this was alluded to in the 24 hour event, Troy Kitch's BDNtv spots that he's done in the recent past, and within the newsgroup chatter regarding DeXter, which is the interim name for the next version of Borland's all-in-one IDE featuring Delphi for .NET / Win32, C# for .Net, and, now, C++Builder for Win32.
Finally we will see all the benefits of the latest Delphi IDE provided within C++Builder at the same time (and in the same box). No longer will there be a 6 month to 2 year wait for C++Builder to catch up to Delphi. And, for C++Builder developers who want to garner greater audience interest in components that they may wish to develop, the combination of C++Builder and Delphi will be provide to be an invaluable pair! However, for the component developer, what may be required is a williningness to develop those VCL components in Delphi32. I know it would be wonderful to develop C++ VCLs that can be used by the Delphi -- and maybe that's a possibility down the road, but at least for now, the component develop tool that will be a welcomed addition to our "integrated" tool box will be Delphi. And while we learn to spin VCLs in Delphi, we can benefit from it using our preferred project specific development tool (i.e. language environment) -- C++Builder.
In the past, you would have to own two separate SKUs - Delphi and C++Builder -- and even with that you may have a version gap issue. But now, from what I can tell, we will have it all in one box and unified in regards to version. This Visual Studio type capability is something I've been wanting for quite some time where IDE's between Delphi and C++builder are finally the same, and there's greater opporutunity to leverage from each language and common (albiet Delphi-based) VCL set.
My guess is that Delphi as a VCL component development language, could get more use than ever before, but that's not lessening the value that C++Builder provides. On the contrary. Perhaps we may begin to see more Delphi developers begin to develop and use C++Builder for more of their projects too. And perhaps, one day, we might see include inline C++ code inside a Delphi app, and, as a result, VCLs of the future could actually be C++ based.
Finally we will see all the benefits of the latest Delphi IDE provided within C++Builder at the same time (and in the same box). No longer will there be a 6 month to 2 year wait for C++Builder to catch up to Delphi. And, for C++Builder developers who want to garner greater audience interest in components that they may wish to develop, the combination of C++Builder and Delphi will be provide to be an invaluable pair! However, for the component developer, what may be required is a williningness to develop those VCL components in Delphi32. I know it would be wonderful to develop C++ VCLs that can be used by the Delphi -- and maybe that's a possibility down the road, but at least for now, the component develop tool that will be a welcomed addition to our "integrated" tool box will be Delphi. And while we learn to spin VCLs in Delphi, we can benefit from it using our preferred project specific development tool (i.e. language environment) -- C++Builder.
In the past, you would have to own two separate SKUs - Delphi and C++Builder -- and even with that you may have a version gap issue. But now, from what I can tell, we will have it all in one box and unified in regards to version. This Visual Studio type capability is something I've been wanting for quite some time where IDE's between Delphi and C++builder are finally the same, and there's greater opporutunity to leverage from each language and common (albiet Delphi-based) VCL set.
My guess is that Delphi as a VCL component development language, could get more use than ever before, but that's not lessening the value that C++Builder provides. On the contrary. Perhaps we may begin to see more Delphi developers begin to develop and use C++Builder for more of their projects too. And perhaps, one day, we might see include inline C++ code inside a Delphi app, and, as a result, VCLs of the future could actually be C++ based.
0 Comments:
Post a Comment
<< Home