Our main product is in Delphi. We got 20+ year old code and brand new code in production. Several hundred forms/windows, ~1MLOC. We're serving a few hundred businesses in a niche (~75% market share).
However we're working on migrating to .Net, though the full transition will take many years. Main limitation is that UI design and such is just nowhere near what we got in Delphi. We're quite used to being able to whip up a non-trivial UI in a day.
So for now we're just moving the "backend" stuff to .Net, doing RPC to our .Net service and similar.
Same here. More than ten years I've moved to Java as replacement since it was the best next thing. It has a practical WYSIWYG GUI editor but still nowhere the fantastic quality of Delphi and just dead nowadays too.
A GUI written in Delphi would function natively in any Windows and then run any Mac or Linux through Wine without troubles.
Just wondering aloud - wouldn't it be easier to port the .dfm parsing to your desired language of choice and keep designing forms in Delphi?
I can only imagine that it's not just the ease of design part (and legacy code) that keeps you in Delphi, it's the whole aspect of it being integrated with writing code, components, units and fast compilation.
We rely quite heavily on DevExpress components, but yeah dfm parsing is something I've considered. But I have this gut feeling while it might get you 80% there you'll spend a ton of time fixing the last 20%, negating the win.
Our main product is in Delphi. We got 20+ year old code and brand new code in production. Several hundred forms/windows, ~1MLOC. We're serving a few hundred businesses in a niche (~75% market share).
However we're working on migrating to .Net, though the full transition will take many years. Main limitation is that UI design and such is just nowhere near what we got in Delphi. We're quite used to being able to whip up a non-trivial UI in a day.
So for now we're just moving the "backend" stuff to .Net, doing RPC to our .Net service and similar.