People were definitely asking for it.

This is kind of the opposite of Go. Not giving people what they are asking for.

There are pros and cons of course. You don't have 17 different ways to iterate over an array, so that's nice. But you also went 13 years without generics, despite them being one of the most requested features, because the designers didn't want that complexity inside Go.

Overall I think Go is better for this philosophy but there are times where the language is clearly written more for its maintainers than it's users.

Mostly safe, contrary to other safer languages, Go memory model doesn't prevent data tearing.

go data races aren't memory safe

(removed)