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 552231
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: My thoughts on Go
by lucas_maximus on Tue 12th Feb 2013 18:22 UTC in reply to "RE[3]: My thoughts on Go"
lucas_maximus
Member since:
2009-08-18

I don't think it does in the first few paragraphs I knew I would absolutely hate it.

Silly implied naming conventions, lack of proper encapsulation just turned me straight off.

Edited 2013-02-12 18:23 UTC

Reply Parent Score: 3

RE[5]: My thoughts on Go
by satsujinka on Tue 12th Feb 2013 18:29 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