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/
-
-
same time as Ruby 1.9.2 (same week) and already had full support for Ruby 1.9.2. For reference, Ruby, like Python, made a major String 4/
-
change in Ruby 1.9, which moved Strings from "bags of bytes" to codepoints with tagged encoding, which means good UTF-8 support 5/
-
the difference is that Ruby did a lot to keep the new String compatible with old String (BINARY encoding and compat hax for just-ASCII 6/
-
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
- 5 more replies
New conversation -
-
-
not sure what 30% adoption means, but
is used in way more places than ruby, which is mostly fast moving web dev (rails really) -
I was just citing
@eevee, who accepted Zed's claim of 30% without disagreement.
End of conversation
New conversation -
-
-
*cough* Github's fork *cough*
-
of course the existence of a single fork in a large ecosystem says very little about overall adoption characteristics.
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.