2 ms·
100% great advice, but really better go with Avalonia, Uno, WPF, Windows Forms, WinUI 3.0 only if one is a Microsoft employee. https://github.com/microsoft/mic
by pjmlp 2y ago
100% great advice, but really better go with Avalonia, Uno, WPF, Windows Forms, WinUI 3.0 only if one is a Microsoft employee.
https://github.com/microsoft/microsoft-ui-xaml/issues https://github.com/microsoft/microsoft-ui-xaml/issues
https://github.com/microsoft/WindowsAppSDK/issues https://github.com/microsoft/WindowsAppSDK/issues
https://github.com/microsoft/CsWinRT/issues https://github.com/microsoft/CsWinRT/issues
https://github.com/microsoft/cppwinrt/commits/master/ https://github.com/microsoft/cppwinrt/commits/master/
- neonsunset 2y agoI was going to complain how Avalonia still has issues with large binaries even with NAOT but I just tested it on https://github.com/sourcegit-scm/sourcegit https://github.com/sourcegit-scm/sourcegit on Windows, and the resulting size of the folder without symbols (the binary and like 4 dlls) is ~55MiB. The binary itself is 41MiB which is as much as Qt6-based qBitorrent binary takes on Windows. So it seems while Avalonia works well enough on macOS, the size of binaries and memory consumption are higher than on Linux and Windows huh.
- pjmlp 2y agoFair enough, although I trust them more to sort out those issues, than to keep waiting for Project Reunion to deliver what was promised at BUILD 2020, or by C++/WinRT team at CppCon 2017 (which is WinUI 3.0 foundation).