Type inference and operator overloading often leads to less-readable code.
IMO when evaluating programming languages, we should not only consider writability but also its readability. This is especially true if many engineers are going to be involved in the development.
It is good to have type inference and operator overloading in terms of writability. Nobody wants to type verbose code.
OTOH some verbosity within the source code helps reading the code. And type information (which type inference and operator overloading tries to hide) is one of them.
So I can respect Go's decision not to support operator overloading / only support some part of type inference.
IMO when evaluating programming languages, we should not only consider writability but also its readability. This is especially true if many engineers are going to be involved in the development.
It is good to have type inference and operator overloading in terms of writability. Nobody wants to type verbose code.
OTOH some verbosity within the source code helps reading the code. And type information (which type inference and operator overloading tries to hide) is one of them.
So I can respect Go's decision not to support operator overloading / only support some part of type inference.