Linked by Thom Holwerda on Mon 11th Feb 2013 22:59 UTC
General Development "I feel like writing about the Go programming language (or 'Golang') today, so instead today's topic is computer stuff. For the record, the language I've programmed the most in has been Python, so that’s the perspective I'm analyzing it from." Some good and bad things about Go.
Thread beginning with comment 552250
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: My thoughts on Go
by satsujinka on Tue 12th Feb 2013 19:29 UTC in reply to "RE[6]: My thoughts on Go"
satsujinka
Member since:
2010-03-11

Previously you hadn't given me much to work with (i.e. what silly naming convention,) but now I think I can actually address your points.

So for starters, it's not really a naming convention. If someone doesn't uppercase their functions/variables/etc. then it's unavailable. You don't really have a choice in the matter, it must be capitalized if you want to use it. (which makes it not a naming convention since there's no choice in the matter.)

So since it's a requirement it quickly becomes very obvious whether something is available or not. This maybe takes some getting used to since caps in other languages are ignored.

As far as I can tell, the Go community doesn't have any issue with it (even on projects) so it doesn't seem like this is a big deal.

Reply Parent Score: 3

RE[8]: My thoughts on Go
by lucas_maximus on Wed 13th Feb 2013 08:48 in reply to "RE[7]: My thoughts on Go"
lucas_maximus Member since:
2009-08-18

I question the readability of this approach.

Edited 2013-02-13 08:49 UTC

Reply Parent Score: 2

RE[9]: My thoughts on Go
by satsujinka on Wed 13th Feb 2013 10:12 in reply to "RE[8]: My thoughts on Go"
satsujinka Member since:
2010-03-11

I question your questioning.

See, doesn't do much for conversation. Provide reasons so we can debate or don't say anything at all.

Reply Parent Score: 2