Live data from Hacker News

Why you should use Go

mortenvistisen.com

71–75 of 75 posts

Re: Why you should use Go

#71
post #30

The author here, thanks for posting this. I can see a lot of people not agreeing with Go, that’s fine, I still love writing it everyday. Taking choices away from you in terms of language features enables you to focus on the problem you’re solving. That makes it a great choice to me.

Can't you just choose to not use a feature?

No, because I'm not the only person writing code. If someone else chooses to use this feature, I will eventually have to interact with it and/or maintain it.

Re: Why you should use Go

#73
post #67

Earlier quoted context omitted.

Mate, come on. I've implied none of that. Just said that the simplicity of Go tends to shift my focus, at least, to the problem and product, not as much the implementation. You like Rust and hate Go, that is very clear. But maybe before you call me arrogant and put words in my mouth, read back my comments. I haven't trashed other languages or told people that what they like is shit. Simply that I like Go, and that I…

It's entirely understandable that you have a different opinion from me; I just don't like the implication that "caring about solving problems" makes one appreciate Go, since that is what nearly all professionals care about. Btw, my opinion isn't just "liking Rust" -- Rust has plenty of problems. My opinion is that Go is uniquely bad among modern programming languages. Most of the major flaws in Go are fixed in every…

But I'm not saying that. I'm not saying that professionals don't care about solving problems. I'm saying that by removing features from a language you tend to shift your focus more to solving a problem vs _how_ to solve a problem (in language space).

When you have lots of options you always have lots of opinions, just human nature. When working with low-level problems I get how having lots of options is good since you need to be precise. But, most people work on web-related problems. These have most likely been solved in one way or another before. I don't want to discuss in PRs if you should use x/y/z language feature, I don't think that's relevant for a lot of technical solutions.

Re: Why you should use Go

#74

Earlier quoted context omitted.

if you think you need to code review for 150 people or your code base will get out of control then it sounds like there’s bigger problems going on

No, I don't think so - because I chose tools like Golang that do the job for me.

I can see how that works for you, but I still find optimizing for stupid depressing.

Re: Why you should use Go

#75
"Go is ripe for Web Development" - not really. See youtube videos by Web Dev Cody or Ben Davis who tried Golang in this context and went back to Ts.

I would say the major strength of Golang is practical community which tends to avoid elegant complexity. The downside is pointers and the lack of null-safety.

Post reply on HN