Live data from Hacker News

Why you should use Go

mortenvistisen.com

11–20 of 75 posts

Re: Why you should use Go

#11

go has excessive verbosity, poor error handling, rough edges for package/dependency management, and forces you to use interface for too many things. it’s not a bad language, but i would not choose it for a new project or base my company around it

I'm really curious, which language is better than Go in those regards? Because I find Go is better than Javascript/Typescript, Java, Python, C++, C# on all of those.

Most people would regards Standard ML as having some very sophisticated ideas in this regard.

Re: Why you should use Go

#13

go has excessive verbosity, poor error handling, rough edges for package/dependency management, and forces you to use interface for too many things. it’s not a bad language, but i would not choose it for a new project or base my company around it

I'm really curious, which language is better than Go in those regards? Because I find Go is better than Javascript/Typescript, Java, Python, C++, C# on all of those.

C# runs circles around Go, imho.

What is it you find better in Go?

Re: Why you should use Go

#15
post #13

Earlier quoted context omitted.

I'm really curious, which language is better than Go in those regards? Because I find Go is better than Javascript/Typescript, Java, Python, C++, C# on all of those.

C# runs circles around Go, imho. What is it you find better in Go?

Go is limited. There are too many ways people in my company can fuck up C# code, it's much harder to spend time moving around letters with Golang.

Re: Why you should use Go

#16
post #5

What do people use for authentication in Go web applications? To me that’s the big missing piece. Just about everything else is in the standard library.

Check authboss, casbin and casdoor.

Re: Why you should use Go

#17
post #5

What do people use for authentication in Go web applications? To me that’s the big missing piece. Just about everything else is in the standard library.

Depends on your needs but Zitadel can do that for you.

We also have a good oidc library that helps you plug into systems that support open id connect.

Re: Why you should use Go

#18
post #13

Earlier quoted context omitted.

C# runs circles around Go, imho. What is it you find better in Go?

Go is limited. There are too many ways people in my company can fuck up C# code, it's much harder to spend time moving around letters with Golang.

Sure, that's a risk.

But force feeding everyone Go is worse.

Code reviews would be a more constructive approach to the same goal.

Re: Why you should use Go

#19

go has excessive verbosity, poor error handling, rough edges for package/dependency management, and forces you to use interface for too many things. it’s not a bad language, but i would not choose it for a new project or base my company around it

I'm really curious, which language is better than Go in those regards? Because I find Go is better than Javascript/Typescript, Java, Python, C++, C# on all of those.

java and c# are great choices

Re: Why you should use Go

#20

go has excessive verbosity, poor error handling, rough edges for package/dependency management, and forces you to use interface for too many things. it’s not a bad language, but i would not choose it for a new project or base my company around it

I'm really curious, which language is better than Go in those regards? Because I find Go is better than Javascript/Typescript, Java, Python, C++, C# on all of those.

It’s surprising you didn’t mention the most popular language to be invented in the last several years, which while having its own flaws, is superior to Go in all the areas OP listed.
Post reply on HN