I wouldn't classify it as large vs small. It's a better or worse fit depending on how the team writes software. Here is one example: Go has a simple syntax t

I wouldn't classify it as large vs small. It's a better or worse fit depending on how the team writes software. Here is one example: Go has a simple syntax that rarely changes and has been backwards compatible since 1.0. It even has a built-in code formatter to keep things consistent. This means that you can write a service with the confidence that it will compile on the latest version of Go when you need to change it. Even if that is months or years later. Additionally, the dependencies for Go programs are stored on disk, relative to the project, in a simple hierarchy. I can't think of a single other language or package manager that makes it easier to vendor all your dependencies. And I do so for most Go projects I work on (I mostly use it for standalone services, not libraries). Here are the typical steps for reviving a project that I haven't touched for over year: git clone ... cd ... go test ./... This can be very useful for the some teams and utterly useless for other teams.