[slantedview]

This is great, but why do I get the sense that Golang's development is so slow? Ex:

Java: We added structured concurrency and virtual threads!

Golang: We added a min function!

Most of the standard lib still doesn't properly support generics, and at this pace, it will be another 5 years at least before it does.

[physicles]

Touché. When I noticed how happy I was that they added a min function, Stockholm syndrome came to mind.

Tbh I don’t see most of the standard lib benefitting from generics. For example, json.Unmarshal wouldn’t be dramatically better with generics — in practice, I rarely see runtime errors where I passed the wrong kind of thing to that function.

I personally love the slow pace of go development. I love that I don’t need to refactor my code every year to take advantage of whatever new hotness they just added. The downside is that stuff that’s annoying now will be annoying forever (like those times when you want a more expressive type system), but I’m willing to live with that.

[Mawr]

Because great care was taken for the 1.0 release to be a complete design. Most language changes since then have just been fixes. That's why Go 1.0 code is basically the same as Go 1.21 code.