|
|
|
|
|
by brundolf
1519 days ago
|
|
> A lot of error handling procedures are based on reacting to C, which was awful Go's design decisions in general make a lot more sense from this perspective. "X was horrible to deal with in C, how can we make a (reactively) better version?" The problem is a lot of these choices (willfully?) ignore the decades of language innovation that have happened since C. They are incremental, reactive improvements, where it doesn't feel like the designers necessarily stepped back and looked at the bigger picture |
|
I get the sense that the designers have a huge amount of ego from making C what it is today.