[think33]

This slide deck really should be embarassing, because it screams "we aren't very good at this engineering thing."

So, you spent 15 minutes and picked the choice that seemed "coolest" to your team, eh? And your team had never heard of Erlang, it wasn't even in the running, eh? And you started out using ruby, for a Cloud platform? Three strikes, right there.

It's possible to make the case that go is a better choice than erlang. While go doesn't handle concurrency as well, and is a few years, rather than a few decades old, it does have an easier syntax if you're staffed with Jr engineers.

But seriously, how can we take you seriously as a company if reliability is not a consideration? If the fact that erlang, the only language which has been doing concurrency right for 20 years, with a stellar record, is never considered?

This just reinforces the impression that bay area companies are a bunch of lightweights who are not capable of solid engineering, but who succeed because a bunch of VCs put a bunch of money into them, and their biz dev guys make enough noise that it looks like traction and then they get bought by a bigger company that needs to "get in on this new technology".

Picking go is ok. Calling yourself a next-generation cloud platform without having any concern about the key factors that a responsible business needs to offer to their customers, makes you look like clowns.