Nikita Tsukanov

I was answering the benchmarking question. The PR itself is beneficial anyway since it removes extra allocations.

BTW, since our strings are relatively small, we can just use [ValueStringBuilder](https://github.com/dotnet/runtime/blob/main/src/libraries/Common/src/System/Text/ValueStringBuilder.cs) with a stack-allocated initial buffer like [.NET runtime does](https://github.com/dotnet/runtime/blob/ac84ea6e241ad2d2cde346144b2c4b3a5d64fa1d/src/libraries/System.Private.CoreLib/src/System/Reflection/AssemblyNameFormatter.cs#L18)

>WebAssembly See https://github.com/AvaloniaUI/Avalonia/issues/1387#issuecomment-389758464

It should be possible to multi-target `netstandard2.1` and `net48`, but I'm not sure if that's worth the complications.

We are most likely do the React thing at some point and switch from 0.X.Y numbering to X.Y.Z numbering while keeping the X number. The overall quality of the product...

.NET 5 should work with 0.9 out of the box. Window background blur effect from 0.10 isn't yet supported with .NET 5 on Windows

>I was wondering what the current state is for mobile platforms and when they might be finished? 0.11, next year

CJK text display works if you set an appropriate font, like this: >You need to use a font that has Chinese characters. https://github.com/anthonyfok/fonts-wqy-microhei is a good one [WenQuanYiMicroHei-01.ttf.zip](https://github.com/AvaloniaUI/Avalonia/files/5703016/WenQuanYiMicroHei-01.ttf.zip) > >Place...

The major milestone is switching to x.0.0 release scheme, which requires a _somewhat_ stable API/ABI. We are quite happy with API stability measures we've taken since 0.9 and our current...

Please check if you have `libgtk-3.so.0` on your machine.