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.
Why you should use Go
11–20 of 75 posts
Re: Why you should use Go
#12Re: Why you should use Go
#13go 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.
What is it you find better in Go?
Re: Why you should use Go
#14What 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.
Re: Why you should use Go
#15Earlier 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?
Re: Why you should use Go
#16What 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.
Re: Why you should use Go
#17What 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.
We also have a good oidc library that helps you plug into systems that support open id connect.
Re: Why you should use Go
#18Earlier 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.
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
#19go 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.
Re: Why you should use Go
#20go 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.