This is maybe a problem for small open source software projects, but not at organizations where code is vetted with constant review. I claim a lot of problems

This is maybe a problem for small open source software projects, but not at organizations where code is vetted with constant review. I claim a lot of problems like this are solved perfectly well by team-agreed policy. For the same reason you don’t see people writing C functions taking void* everywhere for every problem, you don’t see professional Lisp codebase chock-full of terrible, homegrown DSLs. You will see bad code in Lisp, C, Go, Java, whatever if it goes without review or peer agreement. With that said, since coding in Go is a bit more menial, there’s less policy to make around it.