My impression at the time was that Ruby and Python both caught on with people who were ready to be done with Perl.
And, later, that Go set out to be a replacement for Java, but ended up with one of its major use cases being a replacement for Python for ops and SRE folks who were ready for type checking and built-in multithreading.
My impression at the time was that Ruby and Python both caught on with people who were ready to be done with Perl.
And, later, that Go set out to be a replacement for Java, but ended up with one of its major use cases being a replacement for Python for ops and SRE folks who were ready for type checking and built-in multithreading.