Rust: State of GUI, December 2022
kas-gui.github.io
Rust: State of GUI, December 2022
1–10 of 149 posts
Re: Rust: State of GUI, December 2022
#2wow, really impressive!
Re: Rust: State of GUI, December 2022
#3Sadly Rust for WinUI3/UWP/XAML for Windows GUI - actually modern UIs on Windows - was abandoned or explicitly removed from Rust API bindings by MS.
The listed library only uses the ancient win32 api
Re: Rust: State of GUI, December 2022
#4Sadly Rust for WinUI3/UWP/XAML for Windows GUI - actually modern UIs on Windows - was abandoned or explicitly removed from Rust API bindings by MS. The listed library only uses the ancient win32 api
Any idea why?! I find that the modern WinUI is impossible to use from any language other than .NET.
Re: Rust: State of GUI, December 2022
#5Sadly Rust for WinUI3/UWP/XAML for Windows GUI - actually modern UIs on Windows - was abandoned or explicitly removed from Rust API bindings by MS. The listed library only uses the ancient win32 api
Any idea why?! I find that the modern WinUI is impossible to use from any language other than .NET.
Perhaps that's the plan?
Re: Rust: State of GUI, December 2022
#6Sadly Rust for WinUI3/UWP/XAML for Windows GUI - actually modern UIs on Windows - was abandoned or explicitly removed from Rust API bindings by MS. The listed library only uses the ancient win32 api
Sadly?
I prefer desktop Windows programs to be gdi/win32, they are often the most thought out and optimized for actual desktop paradigms (i.e mouse+keyboard+high res screen) without giant margins, padding and whitespace everywhere and makes use of proper desktop class widgets like treeviews, listviews, tabs, etc.
Re: Rust: State of GUI, December 2022
#7Sadly Rust for WinUI3/UWP/XAML for Windows GUI - actually modern UIs on Windows - was abandoned or explicitly removed from Rust API bindings by MS. The listed library only uses the ancient win32 api
Doesn't surprise me, the folks behind it are the same that caused the deprecation from C++/CX, the very first time that Microsoft had something comparable to C++ Builder in productivity for C++ RAD GUI development.
It got replaced with C++/WinRT, which basically requires one to code like in the good old days of Visual C++ 6.0 alongside ATL, editing IDL files without any kind of VS tooling support and manually merging generated code.
Even the eldery MFC has better VS tooling support and COM authoring APIs than C++/WinRT.
Rust/WinRT is even years away from the C++/WinRT "productivity" in its current state, let along what .NET tooling provides, which by the way is also worse than UWP with .NET Native (e.g. no designer available, and no AOT support).
The reality is that only WinDev folks actually care enough about WinUI, the rest of us have moved on burned by these rewrites, and only a few hardcore advocates keep showing up their community calls.
Re: Rust: State of GUI, December 2022
#8Sadly Rust for WinUI3/UWP/XAML for Windows GUI - actually modern UIs on Windows - was abandoned or explicitly removed from Rust API bindings by MS. The listed library only uses the ancient win32 api
Isn't that what the windows-rs crate is for? Doesn't seem abandoned.
Re: Rust: State of GUI, December 2022
#9wow, really impressive!
An impressive write up and understanding of the available ecosystem and the way various things stack.
Conversely, an appalling advertisement for the state of GUIs with Rust.
Re: Rust: State of GUI, December 2022
#10One thing I'd like to see are Rust bindings for wxWidgets. Contrary to the prevailing opinion, I think wrappers over native toolkits are a fine approach for cross-platform development.