News for hackers. Stuff that matters.
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.