change in Ruby 1.9, which moved Strings from "bags of bytes" to codepoints with tagged encoding, which means good UTF-8 support 5/
"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.