> "Man is it really that slow to compile a hello-world Python GTK app?"
GNOME Builder uses Flatpak - when you press "run" button it does full flatpak packaging and runs the resulting package inside a sandbox. Of course you could still run such app natively, directly from the terminal, in which case it would be pretty much instantaneous :)
Now that a lot of GTK mindshare seems to be moving towards gtk-rs, I have a feeling that it's about to get a lot less instantaneous.
This isn't a swipe at Rust, per se: if you're using Rust you've probably already decided that build speed and portability aren't as important as memory safety and performance, and I'm sure that's often a valid trade-off.
I do think that "dev builds" should be much faster than release builds, and that means building natively should be default.
I believe this is actively being worked on; there's a compiler backend being built using Cranelift instead of LLVM that will supposedly improve debug built times by a fair amount, and then the full release builds will switch over to the LLVM-optimized version. Last I saw, the improvement between the existing rustc and Cranelift-based one was something like 15%, but that may have changed in the interim.
Indeed - however, I'm usually compiling things straight on the phone, it's not that slow. Rust can be challenging in this regard, but works acceptably well once you get dependency crates already compiled (which can require adding some swap, unfortunately).
GNOME Builder uses Flatpak - when you press "run" button it does full flatpak packaging and runs the resulting package inside a sandbox. Of course you could still run such app natively, directly from the terminal, in which case it would be pretty much instantaneous :)