Borland C++ Builder (2015)
runtimeterror.com
Borland C++ Builder (2015)
1–10 of 55 posts
Re: Borland C++ Builder (2015)
#2Re: Borland C++ Builder (2015)
#3Re: Borland C++ Builder (2015)
#4Embarcadero is pretty much in the business of soaking customers locked into Borland's old products for as much as they're willing to pay, hence why the IDEs cost an arm and a leg while competitive products are relatively cheap or free.
And maybe by .NET 9, all the kinds of Delphi workloads will be finally supported by Native AOT and low level coding capabilities.
All enterprise products cost an arm and a leg, and at that level it hardly matters, license costs aren't where usually project budgets get burned.
Re: Borland C++ Builder (2015)
#5The component palette was identical to Delphi (and was still Object Pascal code). You could use Delphi UI components with it.
C++ support was a bit buggy in places, but not terrible. I had worse problems compiling C++ on AIX.
Delphi and C++ Builder were simply the best native UI creation tools I've ever used.
Re: Borland C++ Builder (2015)
#6Community edition: https://www.embarcadero.com/products/cbuilder/starter
Professional https://www.embarcadero.com/products/cbuilder
Re: Borland C++ Builder (2015)
#7My main problem with delphi: it is "too proprietary". It was a very productive IDE in the 90's or early 2000's but lost their path and never recovered.
Some new versions broke compatibility with previous version's components. There was the case where you paid a good amount of money on some proprietary components and they simply wouldn't work in the next version: you were imprisoned in an obsolete IDE. By not being multi-platform (I heard it improved lately) you could only use it with/for win32 so it lost servers, embedded, cloud and mobile. By not being open-source nobody could improve it.
Then it had to compete with "native tools". Whoever develops for windows wouldn't quit ms' tools to use it, whoever develops for mac wouldn't quit apple's tools to use it, whoever develops for android wouldn't quit google's tools to use it, whoever develops for linux was mostly ignored after kylix.
Note that I didn't even mentioned price and license.
They improved it later, I heard. But seems more like the old case of too little too late. Most successful programming languages today are open source and multi-platform. Delphi was dependent on win32 for too long and it still is "too proprietary". You do the world a favor by porting your project to lazarus.
Re: Borland C++ Builder (2015)
#8I used to work at a Delphi shop that switched to C++. Of course we used C++ Builder. The component palette was identical to Delphi (and was still Object Pascal code). You could use Delphi UI components with it. C++ support was a bit buggy in places, but not terrible. I had worse problems compiling C++ on AIX. Delphi and C++ Builder were simply the best native UI creation tools I've ever used.
Re: Borland C++ Builder (2015)
#9Re: Borland C++ Builder (2015)
#10I have to repost https://news.ycombinator.com/item?id=28491963 again: My main problem with delphi: it is "too proprietary". It was a very productive IDE in the 90's or early 2000's but lost their path and never recovered. Some new versions broke compatibility with previous version's components. There was the case where you paid a good amount of money on some proprietary components and they simply wouldn't work in the…