Re:It is ridiculously easy to refactor Go
by mseepgood on Sunday January 27, 2013 @06:00PM
(#5126054)
My suspicion / theory is that most programmers turn on syntax highlighting for the same reason that they have desktop wallpapers: to make their lifes more colorful.
Re:It is ridiculously easy to refactor Go
by alangpierce on Sunday January 27, 2013 @10:32PM
(#5126972)
Good language-aware syntax highlighters do a lot more than highlight keywords and other syntactic things, and can make code more readable in a nontrivial way. For example, Eclipse's Java editor will color things differently based on the scope you pull it from, which lets you distinguish local variables, non-static fields, static fields, and inherited fields. It does a similar thing for method invocations, including a strikethrough for methods marked as deprecated. This saves having to manually go to a bunch of definitions in order to get the proper context when reading code you're not familiar with.
When your externally mandated build process is really slow, you appreciate things like easily noticing an unclosed quote, or a missing */ that was supposed to close a comment.
One of the main selling points of Go is that builds are fast.
Re:It is ridiculously easy to refactor Go
by LeafStorm on Sunday January 27, 2013 @08:52PM
(#5126638)
That doesn't make failed builds any less frustrating. Heck, in Python, you don't even have builds, but getting a SyntaxError on import is still frustrating.
And syntax highlighting is even faster..
Like most languages with modules.
That's a perfectly valid reason in and of itself.
To be honest, I often feel as if I was in a brothel on some blogs with CoffeeRubyNodeScript highlighting. (However, the choice of colors on this one isn't too good either)
Re:It is ridiculously easy to refactor Go
by jimbokun on Sunday January 27, 2013 @10:49PM
(#5127030)
"I would liken it to the use of boldface letters to represent matrices (or vectors) in some math textbook: without this convention, you have to rely a lot more on memory to know what each symbol represents."
This is an excellent comparison, as programming languages probably have more in common with mathematical notation than natural language prose.
I would liken it to the use of boldface letters to represent matrices (or vectors) in some math textbook: without this convention, you have to rely a lot more on memory to know what each symbol represents. Mathematicians and physicists everywhere have found this to be useful.
When you have a huge majority of programmers using syntax highlighting, you have to ask yourself if there is not an instrinsic value to its use and, if so, perhaps try to use it to communicate with the larger community, rather than adopting a cliquish practice.