3 ms·

Sorry, I want to be clear here that this is not intended as a snide/asshole question, what do you mean by > Delphi's workflows for AOT deployment (they killed

by olliej 4y ago

Sorry, I want to be clear here that this is not intended as a snide/asshole question, what do you mean by > Delphi's workflows for AOT deployment (they killed .NET Native), nor C++ Builder (they also killed C++/CX). Specifically in this context what is ".NET Native"? Just the period where they started favoring .NET vs real compilation* - and honestly I never used C++ Builder to think my views or experience of it as a product are super useful for anyone interested in them. My original "real" language was Delphi, and I basically stopped with Delphi 4 I think? (this was a long time ago) - I recall there being a bunch of reasons, but the core fast is that I simply stopped using it. * I personally think as a VM and runtime .net is pretty great, however back then I was using inline assembly for terrible performance stuff and losing that was very sad.

pjmlp 4y ago
.NET Native is the name of the product, still feels like .NET, relies on COM vNext (aka WinRT), compiles and runs like Delphi. https://docs.microsoft.com/en-us/windows/uwp/dotnet-native/ https://docs.microsoft.com/en-us/windows/uwp/dotnet-native/ Basically what .NET v 1.0 should have been all along, had Ext-VOS project not decided to go after Java (using J++), and then eventually adopt COOL, turning it into C# and CLR. C++ Builder allows for Delphi like development, or VB like if you prefer, while having access to the whole C and C++ ecosystem. Only matched for a brief time period by C++/CX, but WinDev mutiny managed to kill it. Both are still available on UWP workloads, specially since WinUI 3.0 and WinAppSDK are limping along, so regardless of the community talks, maybe in two years they reach feature parity if they don't lose focus. So regardless of the official message, Windows 11 and 12 most likely as well, depend on plenty of UWP code.
- olliej 4y ago
  Oh, I know what C++ Builder is, I just never used it in any real or consistent fashion so didn't think my opinion of the product mattered :D Cheers for the detailed response.

by olliej 4y ago

pjmlp 4y ago

.NET Native is the name of the product, still feels like .NET, relies on COM vNext (aka WinRT), compiles and runs like Delphi. https://docs.microsoft.com/en-us/windows/uwp/dotnet-native/ https://docs.microsoft.com/en-us/windows/uwp/dotnet-native/ Basically what .NET v 1.0 should have been all along, had Ext-VOS project not decided to go after Java (using J++), and then eventually adopt COOL, turning it into C# and CLR. C++ Builder allows for Delphi like development, or VB like if you prefer, while having access to the whole C and C++ ecosystem. Only matched for a brief time period by C++/CX, but WinDev mutiny managed to kill it. Both are still available on UWP workloads, specially since WinUI 3.0 and WinAppSDK are limping along, so regardless of the community talks, maybe in two years they reach feature parity if they don't lose focus. So regardless of the official message, Windows 11 and 12 most likely as well, depend on plenty of UWP code.

olliej 4y ago
Oh, I know what C++ Builder is, I just never used it in any real or consistent fashion so didn't think my opinion of the product mattered :D Cheers for the detailed response.