Surely Go has a few idiosyncrasies that can be annoying or glaring to people coming in from different languages. Some are actual practical issues (error bubbling that results in repetitive boilerplate, the capitalization of public functions / variables, implicit interfaces) but others are more like ‘weird but whatever’.

I never paid much attention to the impact of disallowing import cycles. Mutually inclusive packages are a pain to manage by any reference system (self-reference, hint, hint). But I see it can be an issue for your code organization when coming in from a more permissive system. However, in reality it doesn’t restrict anything, just forces some extra creativity on the side to plan your hierarchy.

Also, when talking about channels and go routines, you’re glossing over them skipping that this is the whole point of Go — the first class concurrency constructs. As opposed to Rust, for example, goroutines are cheap to spawn (virtually free, from a system resource perspective) as opposed to threads. You have many more options to sync go routines in Go (waiting for one another or just sync’ing some of them up), whereas in Rust you’re mostly as the mercy of the system.


Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store