zlacker

Yep, most of what the author complains about are trivial issues you could find in any language. For contrast, some real, deep-rooted language design problems with Go are:

- Zero values, lack of support for constructors

- Poor handling of null

- Mutability by default

- A static type system not designed with generics in mind

- `int` is not arbitrary precision [1]

- The built-in array type (slices) has poorly considered ownership semantics [2]

Notable mentions:

- No sum types

- No string interpolation

[1]: https://github.com/golang/go/issues/19623

[2]: >>39477821

>>Mawr+(OP)
There are other choices of languages, that are close to and influenced by Golang. Languages such as Vlang[1] (which addresses several issues mentioned) and maybe Odin[2]. Even more, they are at the stage where advance programmers can contribute or influence them in the ways that they might find satisfactory.

Golang is too far down the road and cemented in its ways, to expect such significant changes in direction. At this stage, people need to accept it for what it is or look elsewhere.

[1]: https://vlang.io/

[2]: https://odin-lang.org/