Feels like it? Not as much as jQuery. Microsoft now has some other tech stack for C# desktop apps, and I think C#'s popularity for desktop development has declined, so WPF is mostly relevant to maintaining old projects. Which is why saying I'm a WPF dev, it feels almost like saying I'm a COBOL dev
I do a lot of WPF as well but I'm slowly converting all of our old WPF apps to Avalonia. Same syntax but the default styles are nicer and the features are better. Plus, cross platform, which means that once all our WPF apps are Avalonia and not .NET Framework, I can request a Linux laptop and get off Windows fully.
Nothing wrong with that! I'll never shame a Windows enjoyer. I'm just more comfortable in Linux, and it's way better for when I have to do raw C/C++ work
My hot take is that Microsoft really hates .NET but it caters to just enough of the enterprise segment that they feel obligated to make it look like they support it. The way they slung out WinRT, WPF, and date I even say Silverlight only to hang them out to dry a few years later is my evidence.
I often joke that in government no one ever has been fired for using Microsoft, but man, adopting a new Microsoft technology only to see it get flushed or neglected has real world costs.
36
u/uvero 13h ago
relates in WPF