Is it? An immense amount of the world’s graphical software is written for native graphical targets like SwiftUI, where the iteration cycle is similarly bound to build times. It’s certainly painful, but I don’t think it’s a non-starter.
replySwiftUI has an incremental compiler with interactive workflows.
replyRust has an incremental compiler. And TMU SwiftUI’s live preview is essentially a very rough approximation of what the actual build would produce; it’s not a suitable replacement for a real build when developing a non-trivial UI.
replyThe experiences still fails short of XCode or Playground, hence why Slint has its own scripting language.
replySure, I don't disagree. It's just not clear to me that developers actually index that heavily on hot reloading to begin with.
replyVarious Rust UI projects have been working towards hot-reloadable capabilities, based on the work from the Dioxus team.
replyIME it's just not really that big of a deal at this point. YMMV, etc.
I am aware, still far away from what something like C++ Builder was already offering in the 1990's, let alone other more modern alternatives.
replyMy rust compiles in the time it takes to switch from my editor to my browser to see the changes incremental recompiles are fast enough imo. Dioxus has hot reloading if you want to go faster and Bevy uses it for hot reloading as well.
replyWith a beefy desktop, or some Apple wonder CPU, right?
reply