Go often attracts similarly problematic people, who prefer to yolo 'script-like' code because it's 'simple' but becomes unmaintainable more quickly at scale. B

Go often attracts similarly problematic people, who prefer to yolo 'script-like' code because it's 'simple' but becomes unmaintainable more quickly at scale. Both languages are becoming far more mainstream, but they are still in the realms of people wanting to play with 'new' languages. The correct answer is to choose a language that is maintainable by most engineers you have, and if you need something else for technical reasons, hire the new engineers first - never impose a new language on engineers without very good reason, and definitely not because "It's simple". It's often not the language that's the problem, but all of the 'clever' ways the 'clever' devs use it.