Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> possibly also for C# and JS

The representation for C# is very much fixed, as it allows, and very commonly uses, direct access into the string buffer as a ReadOnlySpan<char> or a raw char pointer, where char is the type of UTF-16 codepoints.

JS could maybe get away with it.



When you have code that works a lot with strings the cost overhead of building an app on iso-latin-1 but encoding as utf-16 can be substantial.

I think Java moved away from this back around 8, or possibly 9.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: