3 ms·
I write enterprise apps almost exclusively in Ruby and a very small amount of SQL and HTML, but I'm guessing Delphi doesn't have some magical fairy dust that ma
by lojack 10y ago
I write enterprise apps almost exclusively in Ruby and a very small amount of SQL and HTML, but I'm guessing Delphi doesn't have some magical fairy dust that makes SQL unnecessary.
If you told me your stack is as you described, I'd say there's either some serious overengineering going on where you work, or you're solving a very different problem that would have been very complicated even in the Delphi world.
I think you're also vastly underestimating the operational work involved in deploying, maintaining, and syncing thousands of desktop apps in this type of environment. I'm personally happy I only have to get my software running on a couple nodes both with the exact same configuration.
- barrkel 10y agoDelphi used drag and drop and property setting to do most of what you'd do in Rails. Whether it's validation, master-details views, specifying display formats to represent decimal formats as currencies, specify the correct editing control for a database column - all specified as properties on the components representing the connection to the database. You'd then be able to drag and drop columns from the list onto a form, and it would create the correct components depending on type, with appropriate labels, etc. Similarly, drop a grid on a form and get type-aware in-cell editing. Automatic updating of a details view when navigating through a parent data set. Etc. One of the nicest things about Delphi was that you could compile into a single executable that you could deploy without further dependencies. One of selling points of Go, 20 years ago.