3 ms·

I think the way it's meant to be read and understood is as follows: "There may (or may not) be many problems with Go, but building bigger projects is not one o

• stouset 3y ago
  This is actually kind of funny because one of the classical arguments made by gophers eight or so years ago when I first started learning it was that golang's limited abstraction power makes the pain of large codebases obvious enough that teams are incentivized to keep projects small.