Re:Notes on Google's Site Reliability Engineering Book
by bluecmd on Monday April 11, 2016 @06:00PM
(#11475502)
> Python sucks and is useless. Most things that were written in python are now written with Go.
This is simply not true in any way.
Re:Notes on Google's Site Reliability Engineering Book
by packetslave on Monday April 11, 2016 @09:13PM
(#11476507)
True in my area as well. The only new things being written in Python are things that need to interop with other systems that have giant existing Python libraries.
Re:Notes on Google's Site Reliability Engineering Book
by thrownaway2424 on Monday April 11, 2016 @06:08PM
(#11475553)
Well it's a big company. In my area people who propose writing new code in python are either gently corrected or heartily derided.
Re:Notes on Google's Site Reliability Engineering Book
by morgosmaci on Monday April 11, 2016 @06:26PM
(#11475647)
I was an SRE who was most comfortable in C++ who changed ladders to a SWE team who was primarily Java. To be honest it was harder to learn all the team specific stuff than pick up Java.
The reason Python tends to suck is not all really nice libraries are ported to it in any reasonable amount of time. (If you need it, you end up doing the work). Go sucks in new and totally different ways.
Literally nothing at Google except third-party code (like Linux kernel) is written in straight C. C++ is very common, though.
Python sucks and is useless. Most things that were written in python are now written with Go.
I guess your question is about what happens if a C++ expert ends up on a Java team, but I don't really know. I happen to have landed in C++ world, which suited me.