3 ms·

One reason is that it has one of the best cross platform native gui solutions out there. It exists because the research side was focused on teaching programming

by tgbugs 2y ago

One reason is that it has one of the best cross platform native gui solutions out there. It exists because the research side was focused on teaching programming and needed a solution that their students could just install. There is a bit of a learning curve, but once you're over the hump it is just a pleasure to work with. See also things like https://docs.racket-lang.org/gui-easy/index.html https://docs.racket-lang.org/gui-easy/index.html.

darby_eight 2y ago
Word!
SkiFire13 2y ago
> One reason is that it has one of the best cross platform native gui solutions out there. I'm always a bit skeptical of these statements. How does it define "native"? Does it use gtk/libadwaita on Gnome and Qt on KDE? What about windows, does it use Win32, WPF, WinUI2 or WinUI3, all of which could be considered "native"? What about platform-dependent layouts?
- Bogdanp 2y ago
  It's GTK on Linux, win32 on Windows, and Cocoa on macOS.
  - lmz 2y ago
    Is it still a wrapper over wxwidgets?
    - Bogdanp 2y ago
      No, it binds to the frameworks I mentioned above directly.
- kazinator 2y ago
  How one defines "native GUI" is very simple: it uses the native widgets of the desktop OS, rather than custom-painting its own onto a pixel-level canvas. Buttons, input fields, lists/combos, context menus, the file picker dialog, what have you, are from the host system.
  - bananapub 2y ago
    it's not that simple on windows, at least: https://raphlinus.github.io/rust/gui/2022/07/15/next-dozen-guis.html#a-small-rant-about-native https://raphlinus.github.io/rust/gui/2022/07/15/next-dozen-g...