Having spent some time kicking around the Delphi space I got quite into WPF in 2007ish. By 2010 I had not just sworn off it, I'd sworn off Windows entirely. The constant stream of rug-pulls as one bit of MS managed to pull off a political heist over another and - oh no - yet another "latest and greatest" technology was effectively deprecated within 18 months of launch, invalidating all the effort you put in to staying up to date just became a pointless treadmill.

Fortunately Rails was taking off at that point so it was fairly easy to change horses and just ignore it.

▲

PacificSpecific 8 hours ago | parent | next [-]

If I'm writing Windows desktop GUIs I still stick to WPF. Might be Stockholm syndrome but I quite like it.

I don't see the reason to use any of the new ms ui frameworks. Especially if ms themselves don't even really use them.

As far as I know visual studio is still a WPF project so I'm not super worried about it no longer working.

	▲	RajT88 6 hours ago \| parent \| next [-]
		WPF looks much nicer. Personally I find it hard as hell to debug. Winforms just work, and have a well defined set of behaviors. It does not matter that they do not look as nice for most people.
	▲	imron 5 hours ago \| parent \| prev [-]
		That’s not so bad. I still stick to win32

▲

taylodl 7 hours ago | parent | prev | next [-]

Microsoft had a lot of great talent suffering from a lack of leadership and coherent vision. They foreshadowed everything wrong with Big Tech today.

▲

calvinmorrison 5 hours ago | parent | prev [-]

At the same time VB still works and runs, so they don't always rug pull.

▲

rbanffy 5 hours ago | parent [-]

They might have forgotten to pull that rug.

	▲	WorldMaker 26 minutes ago \| parent \| next [-]
		They did pull that rug, twice, in two different directions. 1) VB7 (VB.NET) entirely split the VB developer community. 2) VB6 IDE has not worked well and is entirely unsupported in every Windows after XP. It's generally recommend to build VB6 apps in an XP VM and XP being out of security support it's now a huge "Use at your own risk" and "Do your best to isolate the VM from ever having an internet connection". (Not to mention that installers like Install Shield that still understand VB6' super messy version of COM are generally also out of support and security support.) It was alleged that Microsoft almost dropped the runtime components for VB6 in Windows 11. It starts to feel like only a matter of time before they do.
	▲	int_19h 4 hours ago \| parent \| prev [-]
		Definitely not, since it actually takes quite a lot of red tape to ship something as ancient as MSVBVM60.DLL in Windows 30 years later, and guarantee that it is still working. It's just that it's a piece of tech from back when Microsoft corporate dominance on the desktop was at its peak, and many large companies bought into the then-current tech stack, including VB6. So now Microsoft is stuck maintaining it because those are the customers that bring consistent revenue.