As a former Delphi developer, this is very far from truth, in my experience. Nothing modern beats the ease of RAD with Delphi, where you had actually business people making complex software (with a huge amount of tech debt, of course).
I'm not saying it's better - Delphi sucks for a lot of reasons - but this is the only aspect where it really shines.
Have you tried WinForms? It’s a similar workflow to Delphi except I find C# a lot nicer to work with than Pascal. WPF is also good if you need a program that’s more flexible with being resized, but you have to do your layout in XML rather than drag and drop (although you do still get live updates of what your window will look like while you’re writing the XML).
It is not exactly the same, because even with all improvements taken out from Midori learnings, C# is not on the same C++ like league as Delphi happens to be.
So with VCL/FireMonkey, you get all the RAD like tooling that VB/Delphi are famous for, full AOT, and low level systems programming capabilities, including inline Assembly.
- the license was very expensive and the commercial relationship felt predatory
- new features got added all the time, while long standing bugs weren't prioritized (e.g., mobile apps support)
In the C++ variant (a combination of C++ with Delphi wrappers):
- the compiler(!!) was unstable and crashed a lot, where you had to make small irrelevant changes to your code to make it compile without crashing itself
In general:
- the overall culture around it seemed to attract developers without concern for technical debt, which maybe was a consequence of Delphi's own strengths; i.e., every Delphi project was a big ball of mud that you had to fight against
I'm not saying it's better - Delphi sucks for a lot of reasons - but this is the only aspect where it really shines.