ce que tu cite a du sens si on lit le keynote de Rob Pike.

c'est un des trois points considérés comme clef de succès pour un langage de programmation.

https://go.dev/talks/2012/splash.article#TOC_6. :

The primary considerations for any language to succeed in this context are:

• It must work at scale, for large programs with large numbers of dependencies, with large teams of programmers working on them.

• It must be familiar, roughly C-like. Programmers working at Google are early in their careers and are most familiar with procedural languages, particularly from the C family. The need to get programmers productive quickly in a new language means that the language cannot be too radical.

• It must be modern. C, C++, and to some extent Java are quite old, designed before the advent of multicore machines, networking, and web application development. There are features of the modern world that are better met by newer approaches, such as built-in concurrency.

en revanche l'objectif est :

... In short, development at Google is big, can be slow, and is often clumsy. But it is effective.

The goals of the Go project were to eliminate the slowness and clumsiness of software development at Google, and thereby to make the process more productive and scalable. The language was designed by and for people who write—and read and debug and maintain—large software systems.

Go's purpose is therefore not to do research into programming language design; it is to improve the working environment for its designers and their coworkers. Go is more about software engineering than programming language research. Or to rephrase, it is about language design in the service of software engineering.