2020 Delphi supports five platforms, has 64-bit compilers everywhere, has modern language features, interoperates with C++ through C++Builder, and more. In the past few years especially, we've* seen both a lot of work on it, and increasing interest in using it.
It's modern, and used more widely than one might realise.
* "We've": This is a personal HN account but I work on Delphi and C++Builder.
If we take "rapid application development" out of its trademarked context, applying just its common-sense meaning, and applying it to the year 2020, then the modern tech ecosystem that one would want to integrate with is clearly not C++, but rather maybe JavaScript & the browser ecosystem, Python, and low-overhead JVM langauges like Scala or Groovy.
The next thing that immediately jumps out at me is that the form designer is still using pixel-based positioning, instead of layout managers and units of length that we know from html, like em (fontsize-based), or vh/vw (percent of view-height/view-width), etc.
I was trying to research these things more extensively just now, but giving you my name, street address, company, phone number, and then "Error: Field required: Yes, I would like to receive marketing communications" for downloading the COMMUNITY edition? Come on! Enterprise bloat: Check.
* Hit the installer and switched windows, to let the installer work in the background.
* Installer mysteriously gone.
* Tried to run the programme, and it took some digging to understand that the product seems to be in a half-installed state.
* Re-run the installer. This time, keeping the installer in the foreground. Now it works.
* Started Delphi.
* Dropped a button in the form designer to start playing around.
* Oh gosh. Form designer still using pixel-based layouts.
* Deleted the button.
* Doing some Googling to figure out how to do layout managers, and found an interesting youtube tutorial on something called TGridLayout.
* Dropped a TGridLayout on my form.
* Form Designer now caught in an infinite loop bringing up an Error modal that says "Control TButton($17EE2200) has no parent window. Path: ~TButton($17EE2200)".
Thanks Delphi! See you again, another 10 years from now.
> Oh gosh. Form designer still using pixel-based layouts.
If you build a desktop app, you'll get pixel-based layouts, because that's how Windows works. It is fully high DPI enabled and scalable, so it's not accurate really to call the units pixels. Call them design units or similar.
As you noted there are various layout tools, from containers with various flow behaviours, through to anchors and padding.
What kind of modern language features has it gained?
Now when I think "substantial investment" and then look at your website, what comes to mind is "lock-in nightmare". Sorry, not trying to be cruel, just wanting to give you an honest opinion.
I mean: Picture a development team pouring real efforts into development work, then training end-users to use the final product. That represents a real investment. And that investment is then locked into a vendor, where it's unclear what will happen to that investment if the vendor should decide to change the pricing model or go out of business.
I guess the original Delphi did have that problem, but the world was just a different one in the late 90s. You bought your copy of Delphi on a CD with a perpetual license, and an organization that had lock-in to Windows NT software would see it as a perfectly viable path, to keep those Windows NT systems running for the next 20 years to recoup any investment in software. Plus Microsoft was actually pretty good (and continues to be good) at establishing backwards-compatibility.
Cloud tooling definitely has the problem that vendor financial troubles = a sudden "our incredible journey" and poof, your app is gone. That's something client side apps don't have to worry about.
In a bout of late 90s nostalgia, I convinced my then-employer in 2011 to buy a license for the professional version of Delphi for a software project I was doing, and I was just absolutely shocked about how far it had fallen behind the curve. It seemed that attempting to support a modern tech ecosystem while maintaining some semblance of backwards-compatibility was giving it the worst of both worlds. Add to that enterprise bloat.
I don't know what it's like today, but I sincerely hope that someone will get it back on the right track (or has already done so, as I haven't retried since my experience in 2011).