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/
-
-
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/
-
"necessary" breaking changes once they caused too much upgrade problems. 2/2
-
That definitely helped. But the carrot-and-stick approach of tying in YARV convinced a lot of people to do the work.
-
right, and Py3k choosing to be slower at first definitely didn't help.
End of conversation
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.