News for hackers. Stuff that matters.
Re:The lack of a case against Python 3 by JimDabell on Tuesday November 29, 2016 @04:58AM (#13062041)
> Rough estimate 10% of the world speak English as a first language

ASCII isn't even good enough for that 10% – British people need £, which isn't in ASCII – not to mention things like em dashes, en dashes, and curly quotation marks that word processors tend to add.

Re:The lack of a case against Python 3 by JulianMorrison on Tuesday November 29, 2016 @05:33AM (#13062183)
They're in latin-1 though, which is a byte-per-character encoding.
Re:The lack of a case against Python 3 by herge on Tuesday November 29, 2016 @08:20AM (#13062843)
I don't think anyone who deals with character encodings should encourage latin-1 in 2016 instead of utf8. Fair enough, your old C code will work, but everyone else will hate you.

Except, of course, if you deal with Windows...

Re:The lack of a case against Python 3 by pjc50 on Tuesday November 29, 2016 @09:48AM (#13063306)
.. in which case it's Windows-1252 rather than latin-1. And maybe you have to deal with UCS-2, god help you.
Re:The lack of a case against Python 3 by friendzis on Wednesday November 30, 2016 @03:40AM (#13069301)
Except that encoding depends on your regional settings, which in Baltics is Windows-1257 ;)
Re:The lack of a case against Python 3 by guan on Tuesday November 29, 2016 @07:59AM (#13062740)
Kids these days also use emoji.
Re:The lack of a case against Python 3 by yummyfajitas on Tuesday November 29, 2016 @08:20AM (#13062835)
Re:The lack of a case against Python 3 by rmc on Thursday December 08, 2016 @07:53AM (#13129971)
Emoji have been part of Unicode since 1993 (e.g. ️)