After some work with go, I wouldn't call it simplicity that much. Simplicity has too many implications and expectations and by now, I'd call simplicity context

After some work with go, I wouldn't call it simplicity that much. Simplicity has too many implications and expectations and by now, I'd call simplicity context dependent. In the right context, spring boot can simplify backend code, in the right context, libraries like panda can simplify data crunching algorithms in python. And even as this thread shows, "simplicity" immediately blows up into discussions between the different kinds of simplicity. I rather tend to call what go does regularity and the language design of go does promote said regularity. Regularity in this context means: Go codebases and lots of go code tends to follow very similar patterns. And this in turn makes it simple to digest even complex code bases, at least to me. A go codebase might just contain more code, but chasing some listener on the result of another listener through multiple annotations and config files in a java codebase... yeh. And on top of that, this kind of regularity, as well as the kinda small set of libraries to do something makes it easier to get started with the language in my experience, especially for people who aren't seasoned developers.