3 ms·
It's a similar thing IMO. WPF is understaffed to the point where it might as well be dead in my mind. It hasn't received major new features in a decade. It's c
by ripley12 5y ago
It's a similar thing IMO. WPF is understaffed to the point where it might as well be dead in my mind.
It hasn't received major new features in a decade. It's currently owned by the Windows team (not the .NET team) and they have staffed it with a skeleton crew. They don't even have bandwidth to review most community PRs.
Even the .NET team doesn't get responses to issues they raise on the WPF repo: https://github.com/dotnet/wpf/issues/3811 https://github.com/dotnet/wpf/issues/3811
Adding to all that, WPF has a massive dependency on C++/CLI which means it cannot take advantage of many new .NET features until that is rewritten. And from what I can tell (from the outside) that will never happen.
- pjmlp 5y agoAt least C++/CLI isn't like the C++/WinRT dependency on WinUI/UWP. Editing IDL files without VS tooling just like in the good old COM days pre-.NET, lovely.
- int_19h 5y agoThis is all true, but the framework doesn't just stop working because of that, and the tooling continues to support it. Hell, even WinForms is still chugging along, remaining a valid way to write desktop apps for Windows - and it has been in similar limbo for much longer.
- pipeline_peak 5y agoYeah, but like WPF, very little companies are writing promising new software using WinForms. I stripped my resume of anything WinForm related because I kept getting god damn DoD legacy-ware jobs.
- ripley12 5y agoHmm, I wouldn’t say WinForms is in a similar limbo right now. It's maintained by the .NET team and it gets more attention than WPF. Work is happening to make WinForms compatible with NativeAOT and trimming, I think it will land in .NET 7 or 8. (but yes, true, WPF still works and it gets enough support to keep it limping along)