3 ms·
The app is my old online poker tracker, written with pygtk. I am tempted to move to Qt instead, and for a number of reasons will probably try Go instead. 1) A
by bostik 10y ago
The app is my old online poker tracker, written with pygtk.
I am tempted to move to Qt instead, and for a number of reasons will probably try Go instead.
1) As much as I have traditionally disliked Go's dependency management, with the vendoring support it can be made reasonable
2) I never got python's threading to work properly, which made the UI unresponsive when dealing with database operations; and threading in python is a hack anyway
3) I believe (cough hubris!) that I can simplify the internals by further splitting the architecture
One of the best ideas I ever had was to forego all attempts at subprocess management and just go for DBus and its process autolauncher instead. I mean, have you ever tried to make a fork/exec work from within GTK software without causing X hiccups?
- dilap 10y agoCool stuff. I think the UI library story is still pretty raw, but I've done several backend applications in Go, and I'm pretty much in love. It's a very well-engineered language with a strong appreciation for real-world practicalities.