3 ms·

> The amount of energy Microsoft is pouring into these front-end efforts is pretty incredible. After winforms, silverlight, wpf, webforms and WinUI I don't wan

by flukus 5y ago

> The amount of energy Microsoft is pouring into these front-end efforts is pretty incredible. After winforms, silverlight, wpf, webforms and WinUI I don't want energy, I want to see them focus for more than 5 minutes. The only stable UI tech from MS with any long term support has been Win32 that came out 25 years ago. I predict blazor will be quietly dropped (they won't actually admit it for 5 years), just like the others and you'll be forced to rewrite your software in a few years.

scaladev 5y ago
These blog posts are as relevant as ever. https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost-the-api-war/ https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost...
manigandham 5y ago
Other than Silverlight, the rest are still available today. Microsoft is unmatched in backwards compatibility. How are you being forced to rewrite your software?
- flukus 5y ago
  .net core broke compatibility with many more, c#/.net is now decoupled from MS legendary backwards compatibility. Then you've got things like hiring concerns, $nextJob will want people with $nextTech on their resume, it doesn't matter if something is still technically supported because hiring people willing to work on dead platforms is a tough ask, moreso when the tech is a couple of generations old. This churn isn't happening in a vacuum.
  - manigandham 5y ago
    Again, you do not need to rewrite anything if you don't want to upgrade to .netcore/5.0 because .NET Framework is still supported and has a long lifecycle tied to Windows itself. You can even write C# 1.0 code and it will still compile and run today without any issue. Do you expect software to stand still for decades? Please show which other language stack comes anywhere close to this kind of stability because several of them (go, nodejs, rust) didn't even exist when .NET was first released and running critical systems in major companies. You can still find COBOL and Fortran jobs if you want to avoid anything new, no need to complain about the industry moving on.
DonnyV 5y ago
yup, thats why if I need to do a small desktop app I still use WinForms. Its easy to use, mature and performant. Good enough.

by flukus 5y ago

scaladev 5y ago

These blog posts are as relevant as ever. https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost-the-api-war/ https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost...

manigandham 5y ago

Other than Silverlight, the rest are still available today. Microsoft is unmatched in backwards compatibility. How are you being forced to rewrite your software?

flukus 5y ago
.net core broke compatibility with many more, c#/.net is now decoupled from MS legendary backwards compatibility. Then you've got things like hiring concerns, $nextJob will want people with $nextTech on their resume, it doesn't matter if something is still technically supported because hiring people willing to work on dead platforms is a tough ask, moreso when the tech is a couple of generations old. This churn isn't happening in a vacuum.
- manigandham 5y ago
  Again, you do not need to rewrite anything if you don't want to upgrade to .netcore/5.0 because .NET Framework is still supported and has a long lifecycle tied to Windows itself. You can even write C# 1.0 code and it will still compile and run today without any issue. Do you expect software to stand still for decades? Please show which other language stack comes anywhere close to this kind of stability because several of them (go, nodejs, rust) didn't even exist when .NET was first released and running critical systems in major companies. You can still find COBOL and Fortran jobs if you want to avoid anything new, no need to complain about the industry moving on.

DonnyV 5y ago

yup, thats why if I need to do a small desktop app I still use WinForms. Its easy to use, mature and performant. Good enough.