My opinion.
Go is very powerful but ultimately optimized for server software where crashes and deadlocks can easily self heal and a production engineer can debug what happened. Thats kind of the opposite of what you want for a GUI. You don’t want unexpected crashes, deadlocks, etc. You won’t have the users logs and you won’t even know it’s happening unless you get a report.
Swift, Rust and Zig all are better about avoiding avoiding mistakes which is really important for desktop apps. Zig in particular might be a good option as it’s the simplest of the 3 and interoperable with existing C. Rust has been taking off recently in OSS so if you want a plethora of choices in which GUI toolkit to use then that is a good one too.


Well, don’t let the success of Rust dissuade you. Rust’s design means things like null safety, data race safety, etc are alleviated by the compiler. This means AI tools are less likely to make a mistake which is why it’s widely used by people who use AI. Maybe use AI tools to see if a library you want to use is AI maintained if you wanted to avoid them and it won’t cost you much tokens to do so. Rust also has a good C interop story if you trusted those libraries more. If you love Rust then I’d highly recommend it over Go, C, and C++ for what you want to accomplish. It’s the modern language that can do it all without having to worry about common pitfalls of Go (for GUI development)
Swift does run on Linux and there are libraries for GTK that work, but not on BSD. Similar story to Rust but it is definitely Apple focused.
I’m least familiar with Zig but it’s C interop is so good then you can just assume anything in that realm will work like QT or GTK.