4 ms·

>"They chased EVERY fad that could be chased. Silverlight, UPF, XAML, WPF, Islands, MAUI" Being a wise man I spared myself from this madness long time ago;) Wh

by FpUser 5y ago

>"They chased EVERY fad that could be chased. Silverlight, UPF, XAML, WPF, Islands, MAUI" Being a wise man I spared myself from this madness long time ago;) When I need Windows Desktop App I use Delphi or lately Lazarus that can do both Windows and Linux GUI from a single source and produce native standalone executables.

int_19h 5y ago
WinForms is still around, and works as well as it always did. That or WPF are still the sanest choices for desktop apps in .NET, IMO, so long as you're only targeting Windows. And WinForms specifically resembles VCL a lot.
- FpUser 5y ago
  I skipped .NET bandwagon for desktop completely. Comparatively to Delphi there were exactly zero business reasons for me to move my code or use .NET for new apps. On a technical side there were no gains and numerous limitations.
  - int_19h 5y ago
    On the technical side, the biggest productivity gain is from having a garbage collector. Beyond that, language features: while C# 1.0 started in a spot very similar to Delphi (+GC), it evolved much faster - e.g. getting generics in 2005. But, yes, if you looked at it in 1.x days, it really looked a lot like Delphi libraries with Java-like syntax. So if you were already using Delphi, there wasn't much point.
    - FpUser 5y ago
      >"On the technical side, the biggest productivity gain is from having a garbage collector." 1) I use leak detection tool so no productivity gain in that area. Besides it is burned into my brain to always write deallocation code first before doing any allocations. That is when my classes are not using interfaces that are reference counted. In reality I could hardly remember any instances when memory / resource leak tool showed any. Also I did not have to dance around IDisposable, Weak and object caches shenanigans. 2) Generics - this is great feature but in my opinion it is mostly geared towards libraries writers. Being more of a product / application oriented bar few exceptions I personally do not use it much neither in C++ nor in Delphi (Delphi has generics since 2009).
      - naasking 5y ago
        > 1) I use leak detection tool so no productivity gain in that area. These are never as good as garbage collection. In some cases, not even close.
        FpUser 5y ago
        I consider this statement false
        naasking 5y ago
        Consider it false all you like, the proof is in the pudding: https://www.forbes.com/sites/gordonkelly/2021/11/16/google-chrome-hack-new-attacks-exploits-upgrade-chrome-now/?sh=7531f3bd34d0 https://www.forbes.com/sites/gordonkelly/2021/11/16/google-c...

by FpUser 5y ago

int_19h 5y ago

WinForms is still around, and works as well as it always did. That or WPF are still the sanest choices for desktop apps in .NET, IMO, so long as you're only targeting Windows. And WinForms specifically resembles VCL a lot.

FpUser 5y ago
I skipped .NET bandwagon for desktop completely. Comparatively to Delphi there were exactly zero business reasons for me to move my code or use .NET for new apps. On a technical side there were no gains and numerous limitations.
- int_19h 5y ago
  On the technical side, the biggest productivity gain is from having a garbage collector. Beyond that, language features: while C# 1.0 started in a spot very similar to Delphi (+GC), it evolved much faster - e.g. getting generics in 2005. But, yes, if you looked at it in 1.x days, it really looked a lot like Delphi libraries with Java-like syntax. So if you were already using Delphi, there wasn't much point.
  - FpUser 5y ago
    >"On the technical side, the biggest productivity gain is from having a garbage collector." 1) I use leak detection tool so no productivity gain in that area. Besides it is burned into my brain to always write deallocation code first before doing any allocations. That is when my classes are not using interfaces that are reference counted. In reality I could hardly remember any instances when memory / resource leak tool showed any. Also I did not have to dance around IDisposable, Weak and object caches shenanigans. 2) Generics - this is great feature but in my opinion it is mostly geared towards libraries writers. Being more of a product / application oriented bar few exceptions I personally do not use it much neither in C++ nor in Delphi (Delphi has generics since 2009).
    - naasking 5y ago
      > 1) I use leak detection tool so no productivity gain in that area. These are never as good as garbage collection. In some cases, not even close.
      - FpUser 5y ago
        I consider this statement false
        naasking 5y ago
        Consider it false all you like, the proof is in the pudding: https://www.forbes.com/sites/gordonkelly/2021/11/16/google-chrome-hack-new-attacks-exploits-upgrade-chrome-now/?sh=7531f3bd34d0 https://www.forbes.com/sites/gordonkelly/2021/11/16/google-c...