Live data from Hacker News

Rust: State of GUI, December 2022

kas-gui.github.io

31–40 of 149 posts

Re: Rust: State of GUI, December 2022

#31
post #15

How many of those actually look and behave like native and support accessibility correctly?

The native bindings are the first section on the list, and they work well. If you're concerned about looking and behaving native just use those native bindings.

Re: Rust: State of GUI, December 2022

#34
post #6

Earlier quoted context omitted.

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.

Exactly. Haters gonna hate me but I really liked Windows.Forms (and C#) for development line-of-business desktop apps.

Nah, still quite good, although I personally would go with WPF, Forms is also quite good for what still matters on Windows desktop, just note that on the new runtime (.NET Core) there are still some issues with the out of process designer.

Re: Rust: State of GUI, December 2022

#35
post #18
post #17

Earlier quoted context omitted.

What even is "native" on Windows? Is it Win32? WinForms? WPF? UWP? WinUI? Windows App SDK? There's so many to choose from and they all look and behave differently.

These days the native GUI for Windows is Electron.

Not quite, WebView2, which has the benefit of not dragging Chrome with every single application.

Re: Rust: State of GUI, December 2022

#36
post #20

10 years ago Python was famous for how many web frameworks it had. It seems Rust will be famous for the number of GUI libraries.

Why?

1. Rust is growing in popularity, and a compelling GUI solution is needed

2. These solutions take significant time to incubate, so many of the ones we're seeing emerge have been incubating for months or years, started at a time when there were fewer options.

3. The implications for cross-platform app development with Rust are profound, and offer us a way to break free from the pain-points and shortcomings of the local maximum solutions du jour: Web + Electron and Phonegap-style WebView mobile apps.

Re: Rust: State of GUI, December 2022

#37
Shout out to Dioxus. It's a react clone that provides a really nice experience and can run a web GUI faster than React can. That's quite the accomplishment given the disadvantage of having to use shims to access the DOM.

If you want to choose a single language that can create native GUI's, Rust is probably your best or only choice. Other languages are lacking a good story for either the web or for iOS but Rust works well on both.

Re: Rust: State of GUI, December 2022

#38
post #17
post #15

How many of those actually look and behave like native and support accessibility correctly?

What even is "native" on Windows? Is it Win32? WinForms? WPF? UWP? WinUI? Windows App SDK? There's so many to choose from and they all look and behave differently.

Win32, WinForms, WPF are as good as it gets, and really the only ones that matter.

UWP is deprecated, althought it keeps being the one mostly used on Windows 11, as WinUI still isn't up to its game and keeps collecting issues across all their repos.

Windows App SDK is not a GUI framework, rather the new marketing name for Project Reunion, the porting of UWP runtime infrastructure on top of standard COM without sandoxing and application identity.

Re: Rust: State of GUI, December 2022

#39

Shout out to Dioxus. It's a react clone that provides a really nice experience and can run a web GUI faster than React can. That's quite the accomplishment given the disadvantage of having to use shims to access the DOM. If you want to choose a single language that can create native GUI's, Rust is probably your best or only choice. Other languages are lacking a good story for either the web or for iOS but Rust works…

[deleted]

Re: Rust: State of GUI, December 2022

#40

Sadly 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

win32 api is pretty good. I don't see why you would want anything else for native app development. If you want to use the modern stuff it's far better to develop the UI frontend using Microsoft tools in C# and then use Rust as the backend. In this sense Rust story is not worse than C++ or C.

If a person wants a native gui I guess QT would be worth investigating as well (unless one is concerned by the license).

Post reply on HN