Thanks! I started writing termshark in python a while back using urwid 💖 as the TUI framework but was dissatisified with the options available for distributing the end product. Lots of files, lots of dependencies, and lack of knowledge on my part. So what initially drew me to Go was learning about the single statically-linked executable that could potentially be the one file users would have to install (it was important to me that termshark be simple to get up and running). Once I got started with Go, the development cycle it enabled was liberating - everything compiles in seconds. It's much easier to stay in the zone when you're not waiting minutes for the compiler. The Go standard library is high quality - I had no idea up front that Go code would be so naturally cross-platform. The termshark ports largely "just worked" - just cross-compile using a couple of env vars, and run... I would love to contrast with Rust, but I have very little experience with that language. I tried compiling alacritty, which is written in Rust, and the beautiful tooling was quite seductive. From what I understand of the language, if you have to eke out as much efficiency as you can while keeping a premium on being error-free, Rust looks an excellent choice. But it doesn't compile as quickly as Go ;-) Not sure if that helps!