Some time ago I read all critic articles about Go. And now I have to say that most of them are about of matching of programming habits of authors. Most of them are pretty subjective.
By example, common place for Go critics is absence of generics. But actually some generics are not so generics as they named. They sometimes provide some requirements to object in container. Then what's difference against Go interfaces? So...
I also miss some things in Go, but I prefer to leave a place to grow. Go is pretty young.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Some time ago I read all critic articles about Go. And now I have to say that most of them are about of matching of programming habits of authors. Most of them are pretty subjective.
By example, common place for Go critics is absence of generics. But actually some generics are not so generics as they named. They sometimes provide some requirements to object in container. Then what's difference against Go interfaces? So...
I also miss some things in Go, but I prefer to leave a place to grow. Go is pretty young.