|
|
|
|
|
|
by MereInterest
733 days ago
|
|
|
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. |
|
|