News for hackers. Stuff that matters.
Re:Google Go: The Good, the Bad, and the Meh by cdcarter on Monday February 11, 2013 @11:23AM (#5201521)
Not only is tptacek completely correct, the Go maintainers are completely against code colorizing, so having visual markers in syntax is quite nice.
Re:Google Go: The Good, the Bad, and the Meh by stickfigure on Monday February 11, 2013 @01:05PM (#5202167)
FWIW, this makes me seriously question the sanity of the Go designers. I spent my college career writing code on VT100s, I'm never going back. I am much more productive with an IDE, and the patterns of colors and fonts are a big part of that.

I wonder if Rob Pike is colorblind.

Re:Google Go: The Good, the Bad, and the Meh by tptacek on Monday February 11, 2013 @11:24AM (#5201528)
They're against code colorizing?
Re:Google Go: The Good, the Bad, and the Meh by seanmcdirmid on Monday February 11, 2013 @11:31AM (#5201574)
They mean syntax and semantic highlighting. It's mostly a generational thing that goes along with 80 column line widths on amber terminals.
Re:Google Go: The Good, the Bad, and the Meh by shrughes on Monday February 11, 2013 @07:18PM (#5204362)
It's not a generational thing.
Re:Google Go: The Good, the Bad, and the Meh by papsosouid on Monday February 11, 2013 @11:57AM (#5201758)
I wonder how much of that is older programmers being used to not having highlighting, and how much is younger programmers having never tried programming without it. I think the default assumption is that it is all old people resisting change (hence the 80 columns amber terminals bit), but I'm a younger anti-highlighting example. I am not old, I learned to code with coloured syntax highlighting. I didn't realize how much of a hindrance it is until after I had been programming for years and tried turning it off.
Re:Google Go: The Good, the Bad, and the Meh by waterlesscloud on Monday February 11, 2013 @12:15PM (#5201869)
I'm old enough to have done both, and it doesn't matter much to me one way or the other.

If anything, I think coloring is slightly helpful, but I'm fine without it.

Re:Google Go: The Good, the Bad, and the Meh by seanmcdirmid on Monday February 11, 2013 @09:22PM (#5204830)
Sometimes paradigm shifts are just that and indicate generational pivots. Ask an electrician today to do some wiring without color coded wires and they'll think you are batsh*t crazy, but it probably wouldn't have been so crazy a hundred or so years ago when color wasn't viable. The same thing applies to code; these people grew up programming before color monitors were much of an option.
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).
Re:Google Go: The Good, the Bad, and the Meh by sesteel on Monday February 11, 2013 @11:37AM (#5201621)
I agree that syntax highlighting is useful, but people value different things. Whether a language creator likes syntax highlighting or not says nothing about the quality of the language they created.