3 ms·
We use Delphi to develop and maintain a large Windows desktop application. For that I think it's still pretty darn good. I recently made a new module for our
by magicalhippo 5y ago
We use Delphi to develop and maintain a large Windows desktop application.
For that I think it's still pretty darn good.
I recently made a new module for our program, with ~300 input fields including custom search inputs, several grids and multiple 3-layer deep details (head-detail-subdetail). I got the UI elements down in less than two days, and had the whole module ready for initial testing in a less than a month, UI to DB.
This included a lot of smarts, overview/selection views and other custom dialogs, as well as configurable UI defaults like tabstops, required fields, field colors and default values which vary based on current process (think invoice vs credit note).
So yeah, for that kinda stuff it's still pretty great I think. You might want to buy some components, but Delphi itself is expensive so that shouldn't be a huge issue.
For the other platforms I'm less sold.
I've tried FireMonkey, which is their cross-platform UI framework, and it was tedious and the code did not fill me with confidence (3D math library was mixing various concepts etc). They've had some years to work on it since then, maybe things have improved. But you're forever stuck with non-native on all platforms.
The key issue for me is that if you're planning on writing an application with an expected lifetime of 10+ years, like we are, I feel uncomfortable relying on a closed-source tool chain.
Delphi works today, but I don't know where it'll be in 5 years time. I can most likely get it to compile in a VM, worst case, but will it generate the code I need?