Re:The History and rationale of the Python 3 Unicode model f...
by ilyt on Wednesday December 14, 2022 @04:56PM
(#33991172)
It was unequivocally one of the worst decisions in programming. I wouldn't be surprised if costs of dealing with it would be in the billions now. It occasionally saved a byte on devices with little memory which kinda made sense at a time, but not anymore
[ Parent
| on HN ]
Re:The History and rationale of the Python 3 Unicode model f...
by stabbles on Wednesday December 14, 2022 @05:25PM
(#33991537)
It makes perfect sense when writing and reading strings from disk, since you don’t have to worry where and how to store the integer for the length (#bytes & endianness)
Re:The History and rationale of the Python 3 Unicode model f...
by optionalsquid on Wednesday December 14, 2022 @06:19PM
(#33992281)
Wouldn't endianness be a concern regardless, unless you are literally only reading/writing (null terminated) strings? Which I would imagine to be a much rarer case than writing a mix of data-types or just plain text.