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 552233
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: My thoughts on Go
by satsujinka on Tue 12th Feb 2013 18:29 UTC in reply to "RE[4]: My thoughts on Go"
satsujinka
Member since:
2010-03-11

Personal preferences are bound to differ, but I do write Go in a regular text editor... so take that as you will.

Reply Parent Score: 2

RE[6]: My thoughts on Go
by lucas_maximus on Tue 12th Feb 2013 19:19 in reply to "RE[5]: My thoughts on Go"
lucas_maximus Member since:
2009-08-18

I think my personal preferences are actually important as they are pretty basic criticisms. Which the article basically addresses with "haters will be haters".

While you might be able to write code without an IDE.

I wonder how writing a project would work with Go, with the accessibility modifiers down to the naming convention. While I like naming conventions I do think code should be blindingly obvious to read.

I find it difficult enough (I don't have TFS access to force naming convention conformance ... yet) to get 4 devs to use the same naming conventions.

Maybe Go isn't meant for this, but then I wonder who its target audience is then?

Edited 2013-02-12 19:20 UTC

Reply Parent Score: 3

RE[7]: My thoughts on Go
by satsujinka on Tue 12th Feb 2013 19:29 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[7]: My thoughts on Go
by Alfman on Tue 12th Feb 2013 19:35 in reply to "RE[6]: My thoughts on Go"
Alfman Member since:
2011-01-28

lucas_maximus,

"I think my personal preferences are actually important as they are pretty basic criticisms. Which the article basically addresses with 'haters will be haters'"

Your absolutely right, the author attempts to deflect criticism with immature ad-hominem quotes like the following.

"Controversial with [Internet controversialists]. People who complain about this are complainers. Features like this are useful because they let you know who likes to complain about things for no good reason. Go has a lot of features like this."

I find the attitude unfortunate because it seems to detract from an otherwise reasonable overview of the language.

Reply Parent Score: 3