> you can follow the logic always 100% of the time You can see the bare bones if conditions and for loops sure, but what are they actually trying to do? golang

> you can follow the logic always 100% of the time You can see the bare bones if conditions and for loops sure, but what are they actually trying to do? golang code is very thin - it takes a lot to write to convey a particular piece of logic. What a few lines of map/filter/accumulate/group by in a more expressive language like Java or Kotlin becomes dozens of lines in golang. It becomes challenging to extract the underlying logic and to follow it. Java and Kotlin are strictly superior.