Wow I was wondering what toolkit they were going to use… apparently the answer is “yes”.
wow! I love the technical part of GUI programming, and that, for me, was a great article! props to alex.
so mozilla hasn’t given up on rust after all
The crash reporter has a very unique requirement: it must use as little as possible of the Firefox code base, ideally none!
we already ship GTK with Firefox on Linux to make a modern-feeling GUI, so we can use it for the crash reporter, too.
I’m almost hoping for some GTK-caused crashes. They can enjoy the native look and feel while debugging that!
Maybe then they will learn how to stick fully to logical requirements instead of going for “meh big dependency” and “meh look and feel”.
iced doesn’t support accessibility at all https://github.com/iced-rs/iced/issues/552
slint has some support, but it’s a lot weaker than gtk https://github.com/slint-ui/slint/issues?q=is%3Aissue+is%3Aopen+label%3Aa%3Aaccessibility
p.s. I’m also curious if you have any actual evidence that these two are more reliable than gtk. It’s reasonable to think they might be, but I’d like something more than “they’re written in Rust and have fewer features.”
p.p.s. How many Firefox Linux users even use the Mozilla crash reporter? I know on Fedora, if I crash Firefox, I get the Fedora crash reporter, not Mozilla’s. (edit: apparently they stopped doing that years ago; “Another good example comes from Fedora: they had been using their own crash reporting system (ABRT) to catch Firefox crashes in their Firefox builds, but given the improvements on our side they started sending Firefox crashes our way instead.”)