Python 3 adoption

I have to disagree on the change that broke the ecosystem. I spent quite a bit of time in the nineties hacking code that would not compile because it was K&R and other code was ANSI and the compilers did not like to mix the two.

Officially it wasn't a break in the ecosystem, in practicality it was a major pain in the ass. Trying to get patches upstream was met by "K&R was good enough when I started and I will damn well retire with it." and other phrases. And on some platforms you ended up with weird #ifdef because the K&R code compiled under the new compiler but had a different side effect and vice versa (similar ANSI C would compile on a K&R but did produce the effect the very smart programmer had intended.)

On the rest of your response I can't answer as I don't know enough about Van Rossum's employment or Go. I do agree that I expect that Python2's death will have little to do with Python 3/4/5/etc. [Any more than I find working perl4 scripts in places you would think "Its been 20+ years people..]