Best practices for a new Go developer

Re:Best practices for a new Go developer by throwaway999777 on Wednesday September 02, 2015 @01:29PM (#10160729)

> Anything can be made to look bad by only looking at the negatives, anything can be made to look good by only looking at the positives.

And then you have the faux-"fair and balanced" posts about Go by jerf, which always ends up favouring Go for some inexplicable reason.

[ Parent | on HN ]

Re:Best practices for a new Go developer by jerf on Thursday September 03, 2015 @09:19AM (#10164738)

I like it, because I'm writing network servers for the most part. Don't use it for scientific, numeric, or desktop GUI work. You can find posts on /r/golang where I actively discourage that. The further you get from a network server, the worse off you are.

How much more balanced do you want? If "balanced" looks like advocacy, well, maybe the problem is the community has overshot into the trough of disillusionment: https://en.wikipedia.org/wiki/Hype_cycle

If the community was over-praising Go... no, actually, when the community was over-praising Go, you know, that thing that caused the backlash we're in now... I was more negative. It wasn't the Best Language Ever. It's also not the Worst Language Ever.

And I'm generally against seeing "Library X, BUT IN $X!" on the front page of HN for all values of $X, but, that's a separate discussion.

[ Parent | on HN ]