3 ms·

WPF might be there, but with all the "deprecated - oh not deprecated again - not deprecated but no updates for many years - deprecated again - not deprecated ag

WPF might be there, but with all the "deprecated - oh not deprecated again - not deprecated but no updates for many years - deprecated again - not deprecated again" cycles I'm not going to touch it with 10-meter pole for anything that I need to support - same with anything else related to .NET. Also the UI designer experience for WPF is much worse than it used to be with WinForms - so bad I just wrote the code manually, and at that point I can just write HTML/CSS. But perhaps they fixed that - I left .NET in 2015. It doesn't run in the browser anyways - and the browser is what my customers want, because everyone has a browser, but not everyone has Windows desktop - especially today, when many people don't even own a PC and use something with Android/iOS as their primary computing device.

pjmlp 4y ago
Blend is your friend. The only reason I went back to cloud and Web development, is that pre-covid it was the best way to get 100% remote jobs, so I put up with it. By the way, most of those iOS/Android users are using apps and not Websites.
- YesWeWill 4y ago
  They might be using apps, but my customers don't want to pay for developing for four or more separate platforms (Windows, macOS, Android, iOS - also notice that nobody would develop for Linux), so they solve it by having a single platform - the web. Many of my customers previously had (only) a Windows app but found out that onboarding new customers is much faster (and thus happens more) with web apps. .NET is dead to me, I simply don't trust the platform/libraries to continue existence and receive updates. Also the JS/NPM ecosystem is much larger and that's truly what's keeping me there.
  - pjmlp 4y ago
    Yeah we don't get NuGet packages that only offer a single function...
    - YesWeWill 4y ago
      Much better to have a bunch of one-function packages that you can simply avoid than to have a dead package registry with 1/10 of the useful stuff (so not the one-function packages).
      - pjmlp 4y ago
        With the difference that in 10 years those packages will still have support, just like VB 6 runtime and MFC are still shipping on Windows 11.

pjmlp 4y ago

Blend is your friend. The only reason I went back to cloud and Web development, is that pre-covid it was the best way to get 100% remote jobs, so I put up with it. By the way, most of those iOS/Android users are using apps and not Websites.

YesWeWill 4y ago
They might be using apps, but my customers don't want to pay for developing for four or more separate platforms (Windows, macOS, Android, iOS - also notice that nobody would develop for Linux), so they solve it by having a single platform - the web. Many of my customers previously had (only) a Windows app but found out that onboarding new customers is much faster (and thus happens more) with web apps. .NET is dead to me, I simply don't trust the platform/libraries to continue existence and receive updates. Also the JS/NPM ecosystem is much larger and that's truly what's keeping me there.
- pjmlp 4y ago
  Yeah we don't get NuGet packages that only offer a single function...
  - YesWeWill 4y ago
    Much better to have a bunch of one-function packages that you can simply avoid than to have a dead package registry with 1/10 of the useful stuff (so not the one-function packages).
    - pjmlp 4y ago
      With the difference that in 10 years those packages will still have support, just like VB 6 runtime and MFC are still shipping on Windows 11.