zlacker

[parent] [thread] 1 comments
1. xscott+(OP)[view] [source] 2025-12-06 18:56:13
> It was annoying but if it hadn't happened Python would still be struggling with basic things like Unicode.

They should've just used Python 2's strings as UTF-8. No need to break every existing program, just deprecate and discourage the old Python Unicode type. The new Unicode type (Python 3's string) is a complicated mess, and anyone who thinks it is simple and clean isn't aware of what's going on under the hood.

Having your strings be a simple array of bytes, which might be UTF-8 or WTF-8, seems to be working out pretty well for Go.

replies(1): >>MangoT+C8
2. MangoT+C8[view] [source] 2025-12-06 20:07:06
>>xscott+(OP)
I can't say i've ever thought "wow I wish I had to use go's unicode approach". The bytes/str split is the cleanest approach of any runtime I've seen.
[go to top]