2 ms·
You can spawn a goroutine that immediately waits on a channel, so that it will not actually do anything until you want it to. This seems at least as expressive
by anonymoushn 6y ago
You can spawn a goroutine that immediately waits on a channel, so that it will not actually do anything until you want it to. This seems at least as expressive as a single-threaded switch() primitive. I think it can also express the threaded async pattern you want, but I'm not sure.
- jayd16 6y agoAre there any popular, idiomatic Go UI frameworks I could explore?
- oefrha 6y agoYou can try your luck with https://github.com/avelino/awesome-go#gui https://github.com/avelino/awesome-go#gui I explored the landscape earlier this year when I was building a GUI version of a CLI tool written in Go. I was throughly disappointed by all the “native Go” and non-webview options — narrow selection of widgets with basic functionality missing, UIs ranging from lack of polish to horrendous looking (that makes Java GUIs look like godsend), lots of bugs, etc. I ended up using the Qt binding which, despite its own share of problems, at least worked fairly reliably and didn’t constantly get in my way in every way imaginable: https://github.com/therecipe/qt https://github.com/therecipe/qt
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]