News for hackers. Stuff that matters.
Re:Google Go: The Good, the Bad, and the Meh by spacemanaki on Monday February 11, 2013 @11:31AM (#5201578)
Well Rob Pike did call it "juvenile" and compared it to those colored rods that are used to teach children how to count.

http://news.ycombinator.com/item?id=5125958

Re:Google Go: The Good, the Bad, and the Meh by Jabbles on Monday February 11, 2013 @11:36AM (#5201612)
He was joking.

But still, it's his personal taste to not use it.

Re:Google Go: The Good, the Bad, and the Meh by coldtea on Monday February 11, 2013 @12:03PM (#5201800)
I find I tend to disagree with most of the design decisions of Rob Pike, from minor (like that one), to the more important like the bogus emphasis on compilation speed and the half-baked excuses on not having Generics.

If it was someone else on board in Go, we might have had a vastly better language.

Re:Google Go: The Good, the Bad, and the Meh by Jabbles on Monday February 11, 2013 @12:12PM (#5201850)
That's ok. Nothing wrong with disagreeing.

But it sounds like you don't like Go. As you say, it's heavily influenced by Rob's personal vision of how things should be done. Plan 9, unicode, refusal to complicate the parser etc. They're all decisions that have given Go its (IMO) unique feel. Without Rob we'd have a vastly different language, certainly.

Re:Google Go: The Good, the Bad, and the Meh by coldtea on Monday February 11, 2013 @01:13PM (#5202211)
>But it sounds like you don't like Go.

Well, I like large parts of it though. From major stuff, like the implicit interfaces, the syntax for having methods on structs etc, the simple C like syntax, to minor stuff like the capital letter for exports and gofmt for one and only one formatting. And the promise (which is not yet a reality) of a fast, memory efficient, statically compiled language.

Re:Google Go: The Good, the Bad, and the Meh by spacemanaki on Monday February 11, 2013 @11:49AM (#5201714)
Well his personal taste likely informed the design decision to use capitalization to confer some semantics for a variable.
Re:Google Go: The Good, the Bad, and the Meh by tptacek on Monday February 11, 2013 @11:53AM (#5201734)
I'm not sure I see how capital letters make a language harder to syntax highlight.
Re:Google Go: The Good, the Bad, and the Meh by spacemanaki on Monday February 11, 2013 @12:05PM (#5201811)
It doesn't, and I wasn't arguing that... I was suggesting that if one were to prefer reading and writing code without highlighting, one might be more inclined to design a language such that capitalization carries some semantic weight.

I'm just speculating here. I don't really have an opinion one way or the other, although I don't think anyone's an idiot for having an opinion about it, as the OP does.

Re:Google Go: The Good, the Bad, and the Meh by tptacek on Monday February 11, 2013 @12:10PM (#5201838)
This makes a lot of sense. Sorry, I jumped the gun with my response.
Re:Google Go: The Good, the Bad, and the Meh by papsosouid on Monday February 11, 2013 @12:02PM (#5201794)
It doesn't. But not using one form of visual identifier (colour) could motivate one to use another (case).