Hello again there!
This week, Zed A. Shaw, the author of Learn Python the Hard Way, wrote a blog post that sparked quite a conversation. He urges that anyone who is learning to code, should avoid Python 3 and stick to Python 2. He goes on to point out several flaws in the design of Python 3, and how it has not seen any real adoption in its decade of having been released.
While I’m by no means a Python pro, this got me wondering if Python 3 really is a dead project. After all this time, a majority of projects are still running Python 2, and most operating systems still ship with it as the default version. Some people I know claim to have little knowledge of Python 3, while being considerably experienced with Python 2. It would be sad to see such a beautiful language lose users due to some bad design decisions.
One thing I learned from Python 3’s apparent failure, is that taking a sharp turn that results in a host of breaking changes for your users, is not always a good idea — even less so when your new product cannot coexist with the remains of your previous versions.
Python 3 did it wrong.
ECMAScript 4 did it wrong.
ECMAScript 6 did it right.
Angular 2 did it right.
Wishing you a non-breaking week,