Then again, they're broken like most other "unicode" string types (Java's and C#'s, Python's — default — narrow builds until Python 3.3, Cocoa in some ways, etc...) in that the string "API" produces user-facing "UCS-2 plus surrogates" so it's nothing new under the sun.
Then again, they're broken like most other "unicode" string types (Java's and C#'s, Python's — default — narrow builds until Python 3.3, Cocoa in some ways, etc...) in that the string "API" produces user-facing "UCS-2 plus surrogates" so it's nothing new under the sun.