> first-class concurrency That's an overstatement. Also implicit nulls are not beneficent to anyone. And sum types could have made results (error/success) so

> first-class concurrency That's an overstatement. Also implicit nulls are not beneficent to anyone. And sum types could have made results (error/success) so much nicer. I see no reason to go with nulls at Go's inception, hence I call it a mistake.