WPF VS Skia

Gear up, folks, and test drive this fresh-off-the-lab feature. And should you stumble upon any glitches along the way, don’t hesitate to reach out. Got a bug to report or feedback to give? Send them directly to our dotnet/wpf repository. We’re eager to hear from you, because together, we’re only going to make the experience even better!

I did some research and did not find any proof of the EOL on WPF. In fact, Microsoft just updated the roadmap on WPF 2 months ago.

There’s still room for improvement though. I should add, WPF on .NET Core consumes a lot of memory, due to a memory leak. It was logged by our COO as one of our users was doing a comparison.

have you tried this?

WPF: Licencia MIT.

Some added context: It's a side effect of how variable rendering works in UI library we use. There's currently sadly no way how to disable VRR compatibility, which causes the issue you describe unless you tell your GPU to not treat Playnite as VRR compatible. Some more info here.

WPF is definitely not dead. It may not be the latest shiny thing, but it works, it is maintained (judging by https://github.com/dotnet/wpf or https://devblogs.microsoft.com/dotnet/wpf-on-dotnet-7/), and it is fully and officially supported on the modern .NET platform.

This article only sights a video stream. I think part of the problem with the glacial pace of development is reliance on manual testing. See this comment:

https://github.com/dotnet/wpf/discussions/7130#discussioncom...

> Our primary goal is to ensure reduced turn-around-times for new PRs as well as clear the pending backlog of existing PRs. To that end, we are working on putting appropriate automation in place to reduce the dependency on manual testing as much as we can.

See also the recently updated WPF roadmap:

https://github.com/dotnet/wpf/blob/main/roadmap.md

If you look at the history of this file you can over the years tests have been always been in the backlog.

As for “where projects go to die”, they have 3 features planned for this year: Windows 11 Theming, a new type of folder browser, and null ability annotations. And they say they don’t think they can do them all. Maybe I’m underestimating, but that’s not a lot.

Actually, that's not entirely accurate. The lottie-web library itself doesn't support rendering to WebGL. However, there is a package called canvaskit-wasm that wraps Skia (a graphics engine) with WebAssembly (wasm). This package includes a module called skottie which supports rendering animations into a WebGL surface. However, there is a drawback with this approach: using wasm requires loading a relatively large package, and it's uncertain whether all features are supported correctly, as the official compatibility table that tracks lottie support on different platforms does not include skottie.

Skia is pretty great if you can get it running.

The imgs are mainly used by Tencent QQ and Baidu Tieba users. QQ and Tieba compress imgs by default, so the popular imgs (in China we call them "屌图" or "表情包") would be compressed million of times during the spreading, causing the super low quality. These APPs on Android are using Skia for image processing, which suffering from a legendary bug: result would be more green. The bug was fixed in 2016: https://github.com/google/skia/commit/c7d01d3e1d3621907c27b283fb7f8b6e177c629d

There’s also Skia by Google. Used by Android and Google Chrome.