@washi True, but I brought a similar argument over extension members and we already have versioning and breaking changes with field. So yeah, it would be nice if we could get a lot of cleanups which would be a great benefit in a lot of places but I think MS simply doesn't want to focus on it - so a big one like that, which is only visible to those looking under & caring what is in the hood and not token generators, is not their priority for near future .

@washi Well, there's quite a few places in .net that could benefit greatly from breaking backwards compatibility but MS is extremely shy over it (see extension members) and it results in more and more clutter. The whole assembly format could use a serious revision, but so could other core features like delegates, the disposal implementation or immutability. I doubt though that MS will ever take serious steps and rather goes the easy feature route like with unions.

@blue_fenix People these days are so happy in producing technical debt, rather funny. Just a few decades ago, it was all the rage avoid it.

@uvok MAUI never supported Linux desktop environments, only iOS, Android, macOS and Windows (https://learn.microsoft.com/en-us/dotnet/maui/supported-platforms?view=net-maui-10.0). Their stance on Linux desktop was always make a Blazor app and you can have your app everywhere. Hence I ported all my desktop apps a long tine ago from MS frameworks and after hearing MAUI will not support Linux, it was dead for me too.

@uvok WinForms was always meant to be Windows specific for the .net core release. So it works fine under .net 6 with wonkey support in VS64 but it was never considered for a Linux release cause its considered a legacy component. I would recommend using Avalonia or Uno instead, which are way better desktop UI libs anyway. Now the reason why MAUI has no Linux support is prob more down to internal MS politics - that said, their current one seems slop everywhere, so no idea if that's still the case.

@aurisc4 Yeah, it's completely silly. Even worst, because extension members were a hack that follows us till today, we also have Count() instead of the the property Count in LINQ.

@devleader You mean "Have you ever heard about delegates?" Cause for some weird reasons there was someone who thought combining single and multicast function pointers in one is really a great idea a long, long time ago 🙂

@agentultra If you need a type to make your code readable, you variable naming is sub optimal. So nah, using pretty much exclusively var, never had issues understand my code even after years.