On: Uber Go Style Guide

[kerng]

Probabaly more of an emotional, rather then rational decision. I heard that many Go folks from Google joined Uber.

Looking at the stock, they probably should focus on building new things/better the business model, rather then rewriting things in Go.

[weberc2 → kerng]

I'll bite. Why do you suppose it's an emotional decision? And why do you assume they're rewriting things and not writing new code in support of their business model?

[kerng → weberc2]

Because they have publicly talked about it:

https://eng.uber.com/schemaless-rewrite/

[weberc2 → kerng]

From your own link:

> As our business grew, so did our resource utilization and latencies; to keep Schemaless performant, we needed a solution that would execute well at scale.

That's the third sentence. Clearly it was not an "emotional decision" and it was in support of their business model (scale).

[mytailorisrich → kerng]

What else have they got to do, though?

Uber have thousands of engineers to develop and maintain a taxi hailing app...

[ninkendo → mytailorisrich]

Work on their internal chat app, I guess? https://eng.uber.com/uchat/

[xmprt → ninkendo]

That's built on top of Mattermost which is open source. They do build their own infra instead of using cloud though so that probably uses a big part of it.

[mytailorisrich → xmprt]

However you look at it, Uber and other new so-called tech companies these days spend like there is no tomorrow instead of focusing on the bottom line.