3 ms·
Maybe it is just me, but I have a very hard time reading Go in general. I have a hard time with e.g. type annotations without a colon or an arrow. The := operat
by runarberg 2y ago
Maybe it is just me, but I have a very hard time reading Go in general. I have a hard time with e.g. type annotations without a colon or an arrow. The := operator does not read fluently, and I always have to think about what it does to the variable binding (in python the := reads just fine).
Also, whenever I encounter multiple returns it feels very cluttered and I have to stop and think what the heck is going on.
And finally the the capitalization of variable does horrors to my understanding of the code that I’m reading, I know what it is for, but as I’m reading code, if a function being used is an imported from somewhere else is not a meaningful information, and just confuses me.
I bet there is more, but these are some of the examples I’m consciously aware of
- dullcrisp 2y agoThey just sounds like ways it’s different from the language you’re using currently?
- xyzzy_plugh 2y agoI could have written this post, except for exactly everything would be inverted.
- CharlieDigital 2y agoIt's not just you. There is something about Go that feels "off" for me as well. I started picking it up but couldn't get past some of the syntax.