2 ms·
This makes the false assumption that resources put into Python 3 somehow prevented "native browser support," something that has always been firmly in the hands
by pekk 12y ago
This makes the false assumption that resources put into Python 3 somehow prevented "native browser support," something that has always been firmly in the hands of browser vendors and was never blocked by insufficient loyalty to Python 2. The world where just giving up on Python 3 would magically bring huge benefits never existed.
If you don't want to use Python 3, keep using Python 2 through its EOL in 2020+ but why interfere with other people happily using and preferring Python 3 for years now? It is not interfering with you.
- rdtsc 12y ago> 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
- nodejsisbest 12y agoThere were, there were. I think Node.js is the way of the future with their evented IO platform.
- rdtsc 12y ago> I think Node.js is the way of the future with their evented IO platform. But can I use it to build microservices?