Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

C++Builder 11 Community Edition

embarcadero.com

Post reply on HN
Print view View original

21–30 of 76 posts

Re: C++Builder 11 Community Edition

#21

Post by jahnu »

pjmlp wrote: post #6
sirwhinesalot wrote: post #4

Earlier quoted context omitted.

I can definitely understand them wanting to drop custom C++ extensions, but it's a shame they can't figure out how to provide a nice development experience for their newer UI platforms. If only .NET actually works reasonably well with it (and there's a huge managed native overhead) maybe it should have just been WPF 2.0? Not that I would use WinUI anyway, microsoft cannot be trusted with UI frameworks anymore.

The custom C++ extensions argument is a very bad lame excuse, it isn't as if WinRT was ever going to be cross platform, or not every single C and C++ compiler used in production (not toy compilers) doesn't have their own set of extensions anyway. I also don't consider anything related to WinUI/UWP trustworthy for production development, and I used to advocate for it. Stuff like how .NET Native, C++/CX => C++/WinRT tr…

Same. The previous company I worked for we went all in on UWP for our Windows SDK.

An almost complete waste of time as Microsoft failed to deliver on their promises.

Re: C++Builder 11 Community Edition

#22

Post by peterhull90 »

coliveira wrote: post #13

The main problem with Borland C++ is that it is still a 32bit compiler.

Borland C++ is a 32-bit compiler, I believe the latest version is 5.5 and it came out in about 2000.

There is a newer version from Embarcadero, 7.20 from 2016[1].

The compiler in C++Builder is more modern and it will target 64-bit for Windows at least.[0]

[0]: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/C%2B...

[1]: https://www.embarcadero.com/free-tools/ccompiler

Re: C++Builder 11 Community Edition

#24

Post by marcodiego »

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 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: C++Builder 11 Community Edition

#25

Post by blinkingled »

ndiddy wrote: post #18
blinkingled wrote: post #9

Borland's C++ compiler was _fast_. And I mean eye wateringly fast on crappy pre-AMD64 hardware. I wonder if it supports modern C++ today and is still faster than other compilers. (If I am not mistaken this new edition is a offshoot of that?) (Yeah I am not downloading the "Community" edition if I have to provide my name address and phone number. Really if your product needs mindshare and you offer community edition t…

I've downloaded one of their past community editions, their sales team will call and email you. They back off when you tell them you're not evaluating the product for your work, but it's still kind of annoying.

Yeah I figured as much

Re: C++Builder 11 Community Edition

#26

Post by georgehaake »

marcodiego wrote: post #24

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 next version: you were imprisoned in an obsolete IDE. By not being mu…

Delphi 7, that was a lovely vintage...

Re: C++Builder 11 Community Edition

#27

Post by blinkingled »

kwanbix wrote: post #17
blinkingled wrote: post #9

Borland's C++ compiler was _fast_. And I mean eye wateringly fast on crappy pre-AMD64 hardware. I wonder if it supports modern C++ today and is still faster than other compilers. (If I am not mistaken this new edition is a offshoot of that?) (Yeah I am not downloading the "Community" edition if I have to provide my name address and phone number. Really if your product needs mindshare and you offer community edition t…

You don't have an email for spam? And put any phone number.

I keep forgetting my spam email address/passwords lol I have a Google voice number for when I need to use it on forms but I have seen some websites don't accept it - there's ways to determine that it's VOIP it seems.

Re: C++Builder 11 Community Edition

#28

Post by rob74 »

blinkingled wrote: post #9

Borland's C++ compiler was _fast_. And I mean eye wateringly fast on crappy pre-AMD64 hardware. I wonder if it supports modern C++ today and is still faster than other compilers. (If I am not mistaken this new edition is a offshoot of that?) (Yeah I am not downloading the "Community" edition if I have to provide my name address and phone number. Really if your product needs mindshare and you offer community edition t…

Fast for a C++ compiler... but still worlds away from the Delphi compiler!

Re: C++Builder 11 Community Edition

#29

Post by msh »

marcodiego wrote: post #24

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 next version: you were imprisoned in an obsolete IDE. By not being mu…

I think it was C# with winforms that broke the last oppotunity delphi had.

Re: C++Builder 11 Community Edition

#30

Post by codewritinfool »

georgehaake wrote: post #26
marcodiego wrote: post #24

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 next version: you were imprisoned in an obsolete IDE. By not being mu…

Delphi 7, that was a lovely vintage...

Delphi 7 was / is fantastic. Soon after that, they went .NET and the wheels came off.
Post reply on HN