Defenders of Py3: 30% is a pitiful amount of adoption for the amount of time that has passed. That doesn't mean the game is over, but 1/
-
-
Strings), which meant a decent amount of encoding weirdness for a little bit, but, in the long-term, a smooth-enough transition. 7/
-
The summary of the difference is this: In Ruby, it was possible to write a full shim library that worked in both 1.8 and 1.9 for 8/
-
everything that we needed in Rails (I wrote a large amount of it and did a lot of the encoding work in Rails 3). In contrast, Py3.0 9/
-
shipped syntactic changes that were mutually exclusive with Py2.x. This made it impossible for Django to use the shim approach we 10/
-
used in Rails, and which got us on the "latest Ruby" train literally as early as was plausible. If you want to disagree with this 11/
-
analysis, you need to find an explanation for the wide difference in OUTCOMES between Py3 and Ruby1.9. Again, encodings ain't it. 12/12
-
1.9 also shipped with *huge* perf improvements over 1.8, which provided a strong incentive to upgrade. It was still kind of painful.
-
it was painful but reducing the pain was an intentional and concerted effort (I was part of it), including reverting some 1/
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.