4 ms·
Those things aren't being "cute". For example, upper/lower case for exported/unexported is a huge readability benefit. You would be less frustrated if you took
by enneff 8y ago
Those things aren't being "cute". For example, upper/lower case for exported/unexported is a huge readability benefit.
You would be less frustrated if you took the time to understand why these decisions were made, instead of pronouncing them arbitrary.
Go's designers were long-time C users (longer than anyone else in the world, in fact); they had every reason to stick with the way things worked in C, but they deliberately chose to make Go different.
- jzoch 8y agouppercase vs lowercase is not a readability benefit. For someone reading the code an explicit 'pub' or other operator is much more readable, as in "I understand the implications of what I am reading". Many people can skim over it without realizing the difference of the var name case.
- infogulch 8y agoI thought it was weird for 2 months. Hasn't bothered me in the 4 years since. Except [de]serialization at first, and then I got over it when I realized it's worth the verbosity just to be able to flexibly rename things internally while the external interface remains stable.
- enneff 8y agoYou don't see "pub" where a name is used, only where it is declared. Once you've been using Go for a little while the benefits become obvious.
- int_19h 8y ago> Go's designers were long-time C users (longer than anyone else in the world, in fact); they had every reason to stick with the way things worked in C, but they deliberately chose to make Go different. Most criticisms of Go don't come from C perspective, though.
- enneff 8y agoThe ones I'm responding to in this thread do, though.