For DOS development, I loved Borland Turbo C++. But for windows development, Borland's OWL never really clicked with me. I eventually got into windows using MS Visual C++ and MFC.
Borland C++ Builder (2015)
21–30 of 55 posts
Re: Borland C++ Builder (2015)
#22Looks like C++ Builder is still available. Its way expensive and the licensing for community edition is very prohibitive...if you make more than 5k or you have more than 5 people on your team you need to pay up. And you practically need to sell a kidney to afford it. That sucks because this IDE looks really neat, but its def not worth the money in my opinion unless you are a larger company already Community edition:…
Good tools come with a price, and that applies to all industries, not just programming. The most comparable offering would be Microsoft Visual Studio: free up to 5 users for smaller companies. If you have more than 5 users, it’s $45/user/month (for the cheaper Professional edition, but it would be good enough for most). And if you’ve got >250 PCs or >$1M in annual revenue, the 5 free users do not apply.
https://visualstudio.microsoft.com/vs/pricing/?tab=business
https://visualstudio.microsoft.com/wp-content/uploads/2020/0...
Re: Borland C++ Builder (2015)
#23Don't use delphi, the rad sucks for everything but dragging and dropping components. The drag and drop is also a pain in the ass because it will constantly adjust the layout, making every commit be filled with noise. Maybe all frontend is this bad though, I don't have much experience with other tools.
But wouldn't careful usage of margins, anchoring and aligning - if it is possible - take care of this?
Re: Borland C++ Builder (2015)
#24For DOS development, I loved Borland Turbo C++. But for windows development, Borland's OWL never really clicked with me. I eventually got into windows using MS Visual C++ and MFC.
I thought the original OWL with the proprietary syntax for event handlers was great but by the time the second version came around we'd grudgingly switched to MSC++/MFC.
Re: Borland C++ Builder (2015)
#25Earlier quoted context omitted.
Meanwhile, the only real C++ RAD alternative to C++ Builder in 25 years was C++/CX, killed by internal WinDev politics. 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.
>And maybe by .NET 9 If I take look on roadmaps and apply developer velocity of MAUI, WinForms and WPF it will take many more versions.
Avalonia is out there and works nicely. Looks like they're making a WPF compatibility layer.
Re: Borland C++ Builder (2015)
#26For DOS development, I loved Borland Turbo C++. But for windows development, Borland's OWL never really clicked with me. I eventually got into windows using MS Visual C++ and MFC.
I thought the original OWL with the proprietary syntax for event handlers was great but by the time the second version came around we'd grudgingly switched to MSC++/MFC.
Yeah I think the jump from DOS to Windows, procedural to event-driven, lite framework to rich framework, and barely-C++ to very-C++ was just too much for me to tackle at the same time.
Truthfully I first dipped my toes into Windows development using Visual Basic, then jumped to MSVC++ & MFC after I quickly outgrew VB. Having smart colleagues [hi Keith!] and great MFC books [hi Mike Blaszczak!] around certainly made it easier.
Re: Borland C++ Builder (2015)
#27Earlier quoted context omitted.
>And maybe by .NET 9 If I take look on roadmaps and apply developer velocity of MAUI, WinForms and WPF it will take many more versions.
Avalonia is out there and works nicely. Looks like they're making a WPF compatibility layer.
Third party controls are simply not there yet. (Performant datagrids, comboboxes with complex layout etc)
Re: Borland C++ Builder (2015)
#28I have a vague memory of a Borland C++ coming bundled with a rather funky Smalltalk-inspired container library - this was pre-STL and in fact pre-templates even. Perhaps another old fart can confirm or correct?
I think early Borland container libraries had a "Object" base class for everything, pre templates. All that went away as C++ compilers started supporting templates more. I remember this era as always making tradeoffs between code size, memory consumption, standardness and performance. Not sorry those days are over...
Re: Borland C++ Builder (2015)
#29Looks like C++ Builder is still available. Its way expensive and the licensing for community edition is very prohibitive...if you make more than 5k or you have more than 5 people on your team you need to pay up. And you practically need to sell a kidney to afford it. That sucks because this IDE looks really neat, but its def not worth the money in my opinion unless you are a larger company already Community edition:…
They have abandoned community editions - it is several years behind the pro edition, broken on high-DPI monitors, no code-completion/navigation. No plans to release a new version.
Doesn't sound like a winning strategy long-term. From other comments it sounds like they are focusing entirely on customers that are already locked in with them. Eventually though, those customers are either going to go out of business as all businesses eventually do, or they are going to have to move on to other tools eventually.
If community edition is never updated, IDK how they can expect to grow or gain new customers. Thats why Visual Studio updates their community edition so often, because that helps people get familiar with the tools and companies are more likely to adopt them.
Re: Borland C++ Builder (2015)
#30I use the newest version (Alexandria) of C++ Builder everyday in my job since other developers in the company have legacy software from the 90s. You can't really open old projects in new versions of the software. Some devs use VMs to develop on the old versions of Builder. The documentation and the example code for the C++ side are horrible, because they are focused on Delphi. You must know Delphi to figure out how t…
It’s better to port cppbuilder with ui code to Mfc.that’s what we did at last when we were absolutely done with it. As a fellow developer who’d been in this situation before ,my advice would be to start doing it now