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.
MS has abandoned WPF; it's now a "community project".
The hot new thing is Avalonia. It's designed to be a mostly drop-in replacement. I really like it, but I'm also slightly worried they might be going for a commercial rug-pull. I hope I'm wrong, and they just keep the paid extension & consulting model to fund their costs.
Avalonia is a cross-platform technology and it is not by Microsoft but I get what you mean.
It's part of the reason why I think the criticism of Electron apps needs to be contextualized. There is often a pretty darn good reason why people choose to use Electron for desktop apps. You can say what you want about react, I don't like it personally, but it's here to stay and it's much more here to stay than any Microsoft UI technology.
There's GTK, but it's not viable on Windows, and it already starts feeling like a 2nd class citizen when you use anything different from the GNOME desktop environment, while Qt forces you to interact with C++ and have to really care about portability, or you use QML which is much slower.
IMO web based technologies are worse. We're just making Java JVM again in the form of Chromium but with infinite dependencies and half your codebase not being written or controlled by your team.
About the JVM… maybe. I mean, the JVM was never a bae idea. But Java GUI toolkits are so bad, a well-written Electron application typically feels faster, even though the underlying runtime is less efficient than the modern JVM
I tried it a couple years ago. Back then, it was still a little bit too slow and inefficient on desktops. It would not match the performance of a well-written Electron app like Obsidian or VSCodium.
If you can believe it our company runs a Payroll system built in Delphi. Its probably the most bloated piece of junk you have seen. But we somehow get paid by it so I cant complain too much.
I'm a field technician doing laptop installations. All of our programs are Winforms based...they always have this certain "ehh that'll do" kind of look to them
I would have accepted the joke if it was WinForms, but while a discrete amount of JS frameworks have been released since jquery, what are your real alternative in the windows desktop environment?
Yes, there are a few newer alternatives, including ones by Microsoft. And of course, there's always the option of not developing your desktop front end in C#. Even if you need C# for your desktop app, I bet there are quite a few companies that have adopted a stack of C# backend, Electron front end.
45
u/uvero 2d ago
relates in WPF