3 ms·
well, this is good to see, although imho Embarcadero have been pretty disasterous owners of the delphi brand and technologies.
by zabzonk 4y ago
well, this is good to see, although imho Embarcadero have been pretty disasterous owners of the delphi brand and technologies.
- LorenPechtel 4y agoYeah. They were way late on 64-bit support. Yeah, most of us didn't need 64-bit but it was devastating to those who did (note that integrating with a 64-bit application means you need 64-bit support.) That told us we couldn't count on them--from that point on I never started a new project in Delphi and I didn't even reinstall it the last time I rebuilt my machine. C# copied most of the good stuff from Delphi (and, unlike C++, didn't retain the minefield that is C) and since then has gotten almost everything Delphi had. The only thing that comes to mind that C# doesn't have arrays that aren't zero-based. (Delphi supports arrays with arbitrary bounds and supports arrays based on an enum. In C# I'm always casting enums to ints to use them.) Why would I look back??
- pjmlp 4y agoMinus the AOT compilation (NGEN was never taken seriously, and MDIL/.NET native were only for store apps) and we had to wait until C# 7 for the seeds from Midori to give back the low level programing capabilities from Delphi. On the AOT front, .NET 8 still won't be able to cover all .NET workloads.
- t00 4y agoC# also does not have interface implementation delegation which would be a nice to have. Unfortunately both C# and Object Pascal do not support composition over inheritance paradigm well.