Re:Go best practices, six years in
by nedsma on Sunday May 01, 2016 @02:00PM
(#11607145)
I concur. Go syntax is dead simple and even the most basic tools like https://play.golang.org/ can be used without hesitation for some quick and dirt POCs. In the discovery mode, when you're learning a new library, any tool that supports code completion and provides documentation links is nice to have.
[ Parent
| on HN ]
Surprises me it doesn't have syntax highlighting.
Possibly because Rob Pike is not a fan of syntax highlighting, calling it juvenile.
https://groups.google.com/forum/#!msg/golang-nuts/hJHCAaiL0s...
Wow, his second response is really demeaning. Or maybe it's just a shock to me after hanging out in really friendly communities (Elixir etc.) for a while...
Re:Go best practices, six years in
by jasonwatkinspdx on Sunday May 01, 2016 @08:44PM
(#11608575)
On the whole I've found the golang community to be quite positive and enforcing good norms about crappy behavior. I wouldn't assume too much from a post Rob made 4 years ago.
Pike literally quoted a passage from the bible:
https://en.wikipedia.org/wiki/1_Corinthians_13
I won't argue that it was in good taste.
Re:Go best practices, six years in
by QuercusMax on Sunday May 01, 2016 @09:14PM
(#11608655)
If by "literally quoted", you mean paraphrased... Or is this just another case where literally doesn't mean literally?
No. Sorry. I should have linked to the NASB translation, which was the source of his (literal) quote.
https://www.biblegateway.com/passage/?search=1+Corinthians+1...
I feel bad for the person who wanted it on := lines because of sight issues.