4 ms·

Thanks for the analysis! On a side note: might it be the case that the Go codebases you've worked with are just newer/smaller than the Python ones? Do you work

• sudhirj 9y ago
  Think part of the rationale for building Go was to have something that would serve the truly massive scale of the codebase at Google. It seems like they’re already making sure it scales that way.
• sarabande 9y ago
  Yes, I think re:size, I've typically worked in (based on lines of code) larger Python codebases than Go ones, however, I'd still consider the Go codebases large. In terms of legacy code, though, my metric is the following: When I haven't touched code in one year and need to go back to fix something, what language would I want that code to have been written in? I prefer that code to be in a system that's easy and obvious to reason about, i.e. with a type system.