-
Recently, I was chatting with a friend about Avalonia. My friend mentioned that Flutter has abandoned Skia due to Skia’s performance issues and is using the new Impeller instead. He believes that since Avalonia is based on Skia, Avalonia will also have the same performance problems, especially on the mobile phone. But another friend of mine also mentioned that it seems that SkiaSharp and Skia are not exactly the same. Mono has modified Skia so that Skia can take advantage of the high performance of .Net. And he said that it seems that the SkiaSharp used by Avalonia is different from the SkiaSharp of Mono. It seems that the Avalonia team has made further modifications to SkiaSharp to make it perform better. But he also said that this was a rumor, and there seemed to be no such introduction or description on the Internet. I would like to know whether Skia is the same as the Skia currently used by Avalonia except that it uses a different platform? In addition, will Avalonia also encounter the same performance problems that Flutter Skia encountered on the mobile phone? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
well, I think you know the performance of Avalonia? For me it is good enough even on mobile, but still we do much work to improve performance further. SkiaSharp is becomming faster by v3, which is in the oven, see #12604 Last but not least our rendering system is pluggable. This means if there is an issue or someone has way to much time, we can techically add another rendering backend to impeller or whatever. So we are not tied to Skia. For example we had (or is it still there?) a D2D1 render backend on Windows :-) |
Beta Was this translation helpful? Give feedback.
-
I think avalonia team is also experimenting on direct metal support. |
Beta Was this translation helpful? Give feedback.
-
Remember SkiaSharp is just a wrapper |
Beta Was this translation helpful? Give feedback.
well, I think you know the performance of Avalonia? For me it is good enough even on mobile, but still we do much work to improve performance further.
SkiaSharp is becomming faster by v3, which is in the oven, see #12604
Last but not least our rendering system is pluggable. This means if there is an issue or someone has way to much time, we can techically add another rendering backend to impeller or whatever. So we are not tied to Skia. For example we had (or is it still there?) a D2D1 render backend on Windows :-)