“Github is making serious money”

Yea, but the struggled to make a profit. I think that was one of the (explicitly expressed) resons for accepting Microsofts acquisition-offer.

God invented threads for a reason.

Then man invented asynchronous programming so he did not have to use threads 🙂

The problem you describe is mostly due to Python’s of lack of compile-time checking (usually related to no static type checking). There is a bug in the code, and you don’t find out until you run it.

The good thing about Python is bugs related to failing to explicitly handle an error IMMEDIATELY kills the program and gives a traceback pointing at exactly where things went wrong. In Go, a bug related to failing to explicitly check for an error will allow the error to propagate through the program until something really blows up, sometimes long after and far away from where the error really happened, making it very hard to find the real cause.

Note that Python requires you to explicitly ignore an error, Go requires you to explicitly check for an error. So lazy coding mistakes in Python results in errors being raised, but lazy coding mistakes in Go results in errors being ignored.

Go doesn’t “take error checking seriously”, it requires and encourages programmers to “take error checking seriously”, because it’s not going to do it for you.