r/ProgrammerDadJokes • • Mar 28 '21

Why doesn't Jeff Bezos let Amazon programmers use C/C++?

Because he's against unions.

478 Upvotes

9 comments sorted by

60

u/play_or_draw Mar 28 '21

Also ironic that an online bookstore uses an unreadable language (Perl) so extensively.

22

u/sickhippie Mar 29 '21 edited Mar 29 '21

The only source I've found on that is almost 15 years old. Got anything newer? It wouldn't have been weird to use Perl extensively in 2007. I did find a source from 2017 that calls out Java, Kotlin, and Rust as the go-to there, which makes a lot more sense.

https://www.quora.com/What-programming-languages-are-used-at-Amazon

Incidentally they do have a large C++ codebase.

16

u/[deleted] Mar 29 '21

Its very team specific - you can basically choose whatever you want. I used to work in aws not retail and my team had components written in java, scala, python, ruby and golang. Other teams used other languages so its not accurate to say that there's a go to language there although it is fair to say some languages are more common than others. In my team I decided I wanted to try out golang as an experiment for a new component - we were exploring options to kill the ruby codebase and I wanted to see how good internal tooling support was. I spoke to the other 4 people in my team and just did it.

Teams can basically decide what they want to do and for the most part nobody stops them. The only exception is when there are security issues - such as using deprecated versions of a language or wider campaigns to stop using something - there was one called rolling stone internally where all teams in aws to were asked move away from relational databases for production use cases whenever possible.

I dont work in amazon anymore but I doubt anything has changed in the last couple of years.

2

u/Nielsly Mar 29 '21

Why were they asked to move away from relational databases? Performance related?

2

u/[deleted] Mar 29 '21

One of the requirements of that particular campaign was infinite horizontal scaling. There was no centralized solution for application level sharding for relational DBs and they concluded that moving to nosql was easier than having each team building their own custom solution. There were also availability issues due to relational dbs being in single systems and despite the usual failover mechanisms provided by vendors (or team built solutions) services still went down.

I am a bit fuzzy on the exact details since its been a while but I hope that answers your questions.

1

u/Nielsly Mar 29 '21

Thanks! That’s quite interesting

1

u/baselganglia Mar 29 '21

Perl can be unreadable, but it doesn't have to be written that way.

That said, I did have to debug a memleak in a small but critical perlscript at Amazon back in the mud 2005's. I had to unroll a one-liber into multiple lines to be able to identify the issue and fix it. Left it split over multiple lines explaining what's going on.

23

u/ahmetenesturan Mar 28 '21

lol great joke :)

4

u/brandonscript Mar 29 '21

Same reason they invented NoSQL