[gostsamo]

> Compatibility Promise: This makes choosing Go much safer, especially for companies, as it avoids the need for significant future refactorings, as happened from PHP 4 to PHP 5 or from Python 2 to Python 3, for example—more details on the language blog.

Wait until it is time for Go2.0. until then it is comparison of minor vs. major versions.

Overall, this is not a platform description. This is fanboying over ecosystem richness. I'm glad for the author that they've found something they like, but they are a bit off the mark in the post.

[MereInterest]

It also ignores how young Go is as a language. It was released in late 2009, and is 14 years old. Python was first released in 1991. Python 3.0 was released in 2008 (17 years old), but the strong push for migration didn’t start until python3.4 in 2014 (23 years old).

Stability guarantees are never absolute, and can only be evaluated in retrospect. At this point, python 3.x on its own has just as much history of stability as the entire Go language, along with cultural agreement of “let’s never do that again”. On the other hand, if Google had an internal goal that was most easily met by breaking backwards compatibility in Go, I would be very surprised if Go didn’t make that change.