← Back to context Comment by llamataboot 4 days ago just dont ask about unicode 6 comments llamataboot Reply neallindsay 4 days ago Unicode support in Ruby has been great since the beginning. steveklabnik 4 days ago It's a bit weirder than that, in my opinion. Ruby didn't really gain "unicode support" in the sense we mean it today until 1.9.Before that, Ruby did "support encodings" in a sense, but a lot of the APIs were byte oriented. It was awkward in general.https://web.archive.org/web/20180331093051/http://graysoftin... yxhuvud 4 days ago No, it was not great during 1.x times. But it has been fairly good since 2.0 WJW 4 days ago So for at least 12 years then. 2.0 was released in 2013. 0x457 4 days ago Only if you count 1.9.2 as the beginning. What is being talked about is Unicode by default and maybe Unicode tooling (i.e. can correctly iterate over emojis and not just bytes) llamataboot 4 days ago right it was the python string transition i was talking about
neallindsay 4 days ago Unicode support in Ruby has been great since the beginning. steveklabnik 4 days ago It's a bit weirder than that, in my opinion. Ruby didn't really gain "unicode support" in the sense we mean it today until 1.9.Before that, Ruby did "support encodings" in a sense, but a lot of the APIs were byte oriented. It was awkward in general.https://web.archive.org/web/20180331093051/http://graysoftin... yxhuvud 4 days ago No, it was not great during 1.x times. But it has been fairly good since 2.0 WJW 4 days ago So for at least 12 years then. 2.0 was released in 2013. 0x457 4 days ago Only if you count 1.9.2 as the beginning. What is being talked about is Unicode by default and maybe Unicode tooling (i.e. can correctly iterate over emojis and not just bytes) llamataboot 4 days ago right it was the python string transition i was talking about
steveklabnik 4 days ago It's a bit weirder than that, in my opinion. Ruby didn't really gain "unicode support" in the sense we mean it today until 1.9.Before that, Ruby did "support encodings" in a sense, but a lot of the APIs were byte oriented. It was awkward in general.https://web.archive.org/web/20180331093051/http://graysoftin...
yxhuvud 4 days ago No, it was not great during 1.x times. But it has been fairly good since 2.0 WJW 4 days ago So for at least 12 years then. 2.0 was released in 2013.
0x457 4 days ago Only if you count 1.9.2 as the beginning. What is being talked about is Unicode by default and maybe Unicode tooling (i.e. can correctly iterate over emojis and not just bytes)
Unicode support in Ruby has been great since the beginning.
It's a bit weirder than that, in my opinion. Ruby didn't really gain "unicode support" in the sense we mean it today until 1.9.
Before that, Ruby did "support encodings" in a sense, but a lot of the APIs were byte oriented. It was awkward in general.
https://web.archive.org/web/20180331093051/http://graysoftin...
No, it was not great during 1.x times. But it has been fairly good since 2.0
So for at least 12 years then. 2.0 was released in 2013.
Only if you count 1.9.2 as the beginning. What is being talked about is Unicode by default and maybe Unicode tooling (i.e. can correctly iterate over emojis and not just bytes)
right it was the python string transition i was talking about