Re:Retiring Python as a Teaching Language
by rdtsc on Wednesday January 21, 2015 @12:31AM
(#8921646)
> This makes the false assumption that resources put into Python 3 somehow prevented "native browser support,"
Agreed, browser support was probably unrealistic.
However other points still stand.
Python 3 was a mistake. It at the wrong time (too late), and didn't bring enough. The talks, and the time, and drama around it weren't worth to get dict comprehension and unicode support.
A 10x speed improvement (heck, just a 2x) would have been. Better IO handling via something sane like lightweight threads (via an already existing framework like gevent or eventlet). Better packaging. Better default GUI library. Refresh the standard library with something like requests, ipython...
Python had a golden opportunity and it squandered it. There were
Agreed, browser support was probably unrealistic.
However other points still stand.
Python 3 was a mistake. It at the wrong time (too late), and didn't bring enough. The talks, and the time, and drama around it weren't worth to get dict comprehension and unicode support.
A 10x speed improvement (heck, just a 2x) would have been. Better IO handling via something sane like lightweight threads (via an already existing framework like gevent or eventlet). Better packaging. Better default GUI library. Refresh the standard library with something like requests, ipython...
Python had a golden opportunity and it squandered it. There were