4 ms·
This shows that Go does not work in specific scenario (32-bit architecture with fragmented adress space at startup). It says nothing about production readiness
by BarkMore 15y ago
This shows that Go does not work in specific scenario (32-bit architecture with fragmented adress space at startup). It says nothing about production readiness in other scenarios.
- officialchicken 15y agoThe above fact(s) missing from the documentation seem to indicate otherwise.
- BarkMore 15y agoThe inadequacy of the documentation has no impact on the production readiness in the scenarios where Go does work. As a comment above notes, Google is using Go successfully in production. We are also using in production. Production ready != done.
- officialchicken 15y agoGood enough is not the same as done. One data point does not define a trend.
- agentS 15y agoAppengine+Youtube+<everyone-using-Go-in-production> isn't exactly one data point. Each independently is probably a ton of datapoints as services tend not to use one machine. While it is a bummer, I'd argue that the OP is the one that does not define a trend.