How does it bring back productivity when it has the expressivity of C (at least before generics, it’s a bit better afterwards)
C doesn’t have methods, interfaces, closures, newtypes, packages, map or safe slice and string types, or safe automatic allocations.
What bad faith nonsense.
And before generics it could not even implement maps in the language itself, hence my comment.
Re:Go generics are not bad
by germandiago on Saturday July 09, 2022 @02:16PM
(#32037841)
I do not think this is true. Async programming via channels in Go is a big win and way more expressive than what any C library can give you. Also, higher order functions and interfaces are good. On top of that they added generics. I think that it is more than enough of a practical language already.
I feel, programming too often lost productivity with quite a few modern languages. Go brings that back and adds a good amount of modern features, but doesn't get too much distracted by them.