Golang Is Not Ready for Enterprise Systems yet and Here’s Why

medium.com

2 pointsapta4 comments

Open articleView on HN

Article is paywalled - can read here: https://outline.com/PVbd3c

The reasons listed to support the title are:

- Poor error handling

- Manually written SQL

- Reinventing the wheel

- Young and fast evolving technology stack without well-established standards of use

Here are some companies that may disagree with the author:

https://github.com/golang/go/wiki/GoUsers

That some companies are using it is despite the poor fit of golang, not because of it.

That's true, I agree that just because many companies are using a language, it doesn't mean that it's good or suitable. It would be argumentum ad populum, "a fallacious argument that concludes that a proposition must be true because many or most people believe it".

I suppose somewhere in the list are some companies that qualify as "enterprise", which might argue against the claim that Go is "not ready for enterpise systems".

You'd be surprised at their arguments. I've seen golang being used in areas where it is a terrible fit for, and when I ask about why they think it's a good fit, the arguments are very vague, hand wavy, and show the lack of experience (and these are multi-million dollar companies).

Reply on news.ycombinator.com