No x64 Android, no macOS and no Linux support in C++Builder, unfortunately. It could have been a nice solution for cross-platform open source apps, boosting its adoption.
I don't want to be as severe as saying "they botched a release that otherwise could have been gamechanger," but it's very hard to deny x64 Android support is something I've been looking for in a long time from Embarcadero. I jumped straight into the Feature Matrix and got disappointed.
Back in my childhood and teenage years I played with Delphi until Delphi 7 Enterprise, after that the IDE got too heavy for my old computer (the XE release days). Today I have more than enough capable laptop and I don't feel like playing with Delphi anymore because I just moved on, but C++ is a language I appreciate and I'd like to take seriously for mobile development[0].
I'll start to think they whether they are seriously behind in technology to advance the C++ libraries and compiler to these platforms (which makes them, incompetent in terms of market strategy? underfunded?) or that they are deliberately hindering C++Builder, which has always been 2nd-class in front of Delphi (which shoots themselves in the foot?). It's so unfortunate they couldn't/didn't release x64 Android support on this C++Builder release.
I'm not saying Delphi should die, as I said previously: Delphi is the language that got me into programming, before it made me go away thanks to its heavy IDE back then... I loved Delphi, but I don't want to go back to it just to develop mobile apps. I guess I'll keep on my road to Flutter and reading this launch post was just a 5-minute distraction.
--
[0]: I'm well aware I can use Java or Kotlin and then jump into Android NDK, yeah... I just miss using a RAD-type IDE.
To be fair, C++ was never their primary focus. Everything from Borland was Pascal-oriented, even C++ Builder's GUI and components were Delphi-based. Quality of Builder vs. Delphi was worse, compiler performance too. Visual Studio 6 started beating Builder in every aspect except ease of GUI design.
A big part of the value proposition for Delphi was the VCL (no idea the state of such nowadays), and actual sane layout management. But pretty much everything Delphi did with the VCL is part of Cocoa anyway, so you're left with either reusing the VCL and having weird windows UI elements in Cocoa (I'm assuming buttons, etc would be cocoa controls, but <grandpa>back in my day</grandpa> the Delphi community had tonnes of VCL UI components that were all/mostly custom drawn - e.g. windows), or only really using the language itself in which case freepascal exists, so you might as well use that.
Delphi was my first language for actual software, alas (or fortunately?) that code has been lost to the mists of time. But I pretty much bailed Delphi during the Insprise BS (it came at the time I was moving to linux and "adopting" Java and C[++] so from a "keep developers around" PoV the insprise BS was well timed for me to abandon to just say F this).
