4 ms·

> My side project was made in Delphi and quickly surpassed my full-time salary, so I formed my own company. The only reason I moved away from Delphi years later

> My side project was made in Delphi and quickly surpassed my full-time salary, so I formed my own company. The only reason I moved away from Delphi years later was that the database drivers were far less available than in .NET ecosystem (and I make database migration software and need many drivers) Moving to .NET was a pain, but it was obvious that without Anders Hejlsberg Delphi is going to wither down, and .NET is going to thrive and evolve. Woah, this is exactly what happened with me too! Back in 2001 I wrote a security app with Delphi and launched it as a side product. Borland got sold and Delphi became expensive, dotnet became a thing, and the rest was history. Several years later, I'm on the 3rd generation of that security product, cross platform with dotnet core, and I've finally quit my day job to work on it full time! I enjoy working with dotnet and Rider, but I have fond memories of working with Delphi. Compile times were insane, the RAD tools were great, and the IDE just flew - might be rose-tinted glasses, but I don't recall it ever crashing or being slow in any way.

zerr 5y ago
What cross-platform GUI do you use for dotnet core?
- GordonS 5y ago
  None, the product grew from being controlled by a single-user desktop app to a multi-user web-based GUI (built with ASP.NET Core).
metadata 5y ago
Perhaps we have the same glasses :) Delphi did use to crash, but not that much. It had its quirks and we knew which ones they were and it didn't impede us. We now use .NET5 and in some products. WPF for GUI, but new stuff is all made in Blazor. Being on the bleeding edge means that lot of things in .NET was constantly crashing and not working exactly right, that tooling was broken. You would think Microsoft would have more resources for something like Blazor. I have learned since that new tech is made by very small teams and accepted that as a fact of life. Borland really could have saved Delphi, but I guess corporate types started treating their own company as a product, selling it around a few times, and vision was lost.

zerr 5y ago

What cross-platform GUI do you use for dotnet core?

GordonS 5y ago
None, the product grew from being controlled by a single-user desktop app to a multi-user web-based GUI (built with ASP.NET Core).

metadata 5y ago

Perhaps we have the same glasses :) Delphi did use to crash, but not that much. It had its quirks and we knew which ones they were and it didn't impede us. We now use .NET5 and in some products. WPF for GUI, but new stuff is all made in Blazor. Being on the bleeding edge means that lot of things in .NET was constantly crashing and not working exactly right, that tooling was broken. You would think Microsoft would have more resources for something like Blazor. I have learned since that new tech is made by very small teams and accepted that as a fact of life. Borland really could have saved Delphi, but I guess corporate types started treating their own company as a product, selling it around a few times, and vision was lost.