Advice for the next 100 Rust GUIs

29 points by bitshift


travisgriggs

I love Zed, not much of a rust guy at the moment, but maybe some day. Anyway, this:

There’s evidence that the LLM cost of writing Rust code is not significantly higher than other languages, and there is reason to believe that in large codebases, Rust will be more maintainable because its type system helps enforce invariants.

caught my eye. I was actually intrigued to go see the “evidence” (https://danluu.com/pl-tokens/). I actually didn’t find much evidence at this point. The article even concludes with “who knows?”. It’s more of an attempt to validate the claim, and ironically it does it domains (back end type algorithms) where static languages have been more prevalent, and doesn’t test much in the domains (user facing stuff) where dynamic languages have tended to thrive.

I would be curious how compelling some of the others felt the “evidence” was. I actually liked the evidence article a bit (I.e. was grateful for the ref). It just felt like this author is reaching if they see it as a support for what the hope is here.

hawski

Accessibility is not exactly solved. AccessKit may be very good, but its very nature is being a bolt-on. It keeps a yet another copy of the UI control tree internally. A unified rendering/a11y tree is possible, but AccessKit doesn't fit that paradigm AFAIU.

bitshift

I like what he has to say about modularity.

One of the things the web ecosystem has done really well is encapsulation of some of the hard parts of GUIs. If you want to build your own web framework, you don't have to worry about opening a native window, or rendering text, or making widgets accessible. You get all that for free! That lowers the barrier to entry and allows the crowd to thoroughly explore the solution space.

The downside of thoroughly exploring the solution space is we got thousands upon thousands of different web frameworks, and it took a decade for things to settle. But on the whole, I think the competition of ideas was worth it.