As someone that unironically wants to rewrite everything in Rust, but does Java for a living, Go started off horrible, but has become OK. Especially for that sweet spot between “too big for a shell/python script”, but “not big enough to need perfect type checking/advanced tooling”, Go is decent. I recently clobbered together a CLI tool for a customer that does some custom stuff involving S3 files. I disagree with it’s biggest fans that it’s really simple. Some of the syntax seems very weird, the error handling (while better than exceptions) is still extremely tedious and weak.
Honestly, the fact that the creators thought they knew better than EVERYONE ELSE that they didn’t need generics, and argued against it FOR YEARS, just to finally add them now tells me everything I need to know about how they think of their users, and about whether they react in a timely and reasonable manner to needs of the community.
As someone that unironically wants to rewrite everything in Rust, but does Java for a living, Go started off horrible, but has become OK. Especially for that sweet spot between “too big for a shell/python script”, but “not big enough to need perfect type checking/advanced tooling”, Go is decent. I recently clobbered together a CLI tool for a customer that does some custom stuff involving S3 files. I disagree with it’s biggest fans that it’s really simple. Some of the syntax seems very weird, the error handling (while better than exceptions) is still extremely tedious and weak.
Honestly, the fact that the creators thought they knew better than EVERYONE ELSE that they didn’t need generics, and argued against it FOR YEARS, just to finally add them now tells me everything I need to know about how they think of their users, and about whether they react in a timely and reasonable manner to needs of the community.