Why is it not advised to use Borland technologies?

Question

C++ / C#

We study both Visual C++ and C++ Builder in college. So, I'm doing a course paper using the latest technology (required). A little uncomfortable, yes. The price is high. But using the same RAD Studio, you can create a cross-platform application. When they hear about cross-platform, they immediately advise Qt. Since I am a beginner, I would like to learn from experienced programmers why C++ Builder and Delphi are so bad?

Answer 1

1. The C++ compiler was outdated for a very long time. As far as I know, in XE10, quite recently, it was decided (did not check). Slowpoke!
2. Why? Somewhere since 2001, Borland naturally spit on Delphi. Delphi 7 was the best for a long time - until 2010 appeared. The new owners are recovering, but not everything goes as it should (XE4 is really buggy than XE2, I'll still think it's better to keep it under Win10 to work with the .NET environment there).
3. They seem to have bet on the wrong cross-platform framework. FireMonkey is an imitation of standard controls. Slow and buggy. And if for the sake of something you decide to turn off ClearType - generally atas!
4. Free WinForms has taken away a large audience from those who need to quickly write a program for Windows only. But it's more like a VCL analog than FireMonkey.
5. Embarcadero are actually the only ones that support good Pascal.

Answer 2

I'm not a professional, but I think Delphi is dying...

Answer 3

at one time he lost the market because of this, the market for its use is not large, that is, it is difficult to find work on it

Answer 4

everything in nature develops according to a sinusoidal law. Delphi development is no exception. The developers transferred a lot of technologies and ideas from Java
to Delphi, then from Delphi to other languages ​​​​(for example, dotnet went into motion when the "ideologist" moved from Borland to them). Now Delphi is being integrated on the basis of the same DotNet.
It is impossible to say that Delphi is dead. I know quite a few large companies whose product is developed in Delphi. The current ones feed on them (after all, the Embarcadero seems to have sold its asset to someone else) periodically advertising something new. Companies stick to Delphi because of the rather low entry threshold into development.
About cross-platform here the question is rather slippery and contains a bunch of nuances. For example, licensing such a development. Therefore, if you start from scratch, you can really look towards QT. If you have development experience in Delphi and not in QT, and you had to start yesterday, then you should look at offers with this environment.
In each RAD, the principles are based on the same thing: components are wraps of some standard components or someone else's libraries. Because of such attempts to "smooth out" the code bloats exponentially. They also hang some kind of framework. Each RAD has both advantages and disadvantages. For example in DotNet I doubt for example that it is possible to create a dynamic library with exported functions without including a framework and a class tree.
Conclusion: when making a decision, it is necessary to focus on many parameters. First of all, on the requirements of the customer. Secondly, on the experience of the developers of the team. And the technologies are almost the same for everyone and are copied from each other.

Answer 5

Since I am a beginner, I would like to learn from experienced programmers why C++ Builder and Delphi are so bad?

Because this is such a dense creation that it must be forgotten like a bad dream ! ;-)
The last outstanding creation from Borland was Borland C ... 3.1, if I remember correctly, still under MS-DOS. But this is the early 90s. And there was a really outstanding (for those years) compiler and IDE.
But immediately after that, the entire Borland compiler development team, led by Katherine Jensen, went to the established company TopSpeed ​​to develop N. Wirth's Modula-2 language.
And from Borland even then there was one sounding name ... a wrapper.
Delphi was already a freak at the time of its inception.

Answer 6

It's very simple: you don't need to. Open any site with vacancies, for example hh.ru and see what percentage of vacancies with knowledge of the Embarcadero technology stack. Well, if there is one vacancy.

Answer 7

1. Really very "heavy" IDE: wrote myObject-> and wait until it finds what is inside this myObject and throws out a window with methods, everything is frozen input is not displayed ... (this applies to the latest Embarcadero XE> 7)
2. "Dialectisms" of Embarkader's C++. When porting the project to VS, I had to rewrite the code in pieces, because "you don't understand mine".
3. Third-party components are most often not top-down compatible. For example, you have to rebuy TMS (and first wait for the rewrite) with each purchase of a new version of the builder.
4. Glitches and bugs. Always-always-always, when working with a more or less serious project, you get stuck in some bug in a component or compilation - debugging is very unpleasant.
Having worked with builders, from Borland 5 to Embarcadero XE8, I gave up on everything and switched to Qt. Happy.