It means the thing I built to make working with PRs easier, faster, and more reliable, doesn't work in some of the places it would be most useful :/

I've just been caught out by people who have used both on shared projects where these magic values mean different things on different people's machines. I'm against using either.

In that it appears to use a RichTextBlock to render the response, it's worrying that content here can cause an app to crash.
Or is it when trying to generate the content it has an unhandled error?

based on old blog posts about improving WPF performance, I think they stopped optimizing launch time for a while. When they started again, it was after Win11 was out, and so they didn't include Windows 10-related optimizations.

The upcoming lack of updates when it goes out of support is going to be the main reason for me.

If I had the time and inclination and I was only building for Windows, I'd explore using WinForms to show a loading screen and acting as a bootstrapper for loading an app built with another framework.

(More complex apps with many dependencies would load slower)

Not sure if it's due to a presumed knowledge/authority or people too busy or the fields moving too fast to keep up with what others are doing/saying/thinking