tag:blogger.com,1999:blog-3460761117713509776.post6541414483357246060..comments2016-03-10T12:56:30.576-08:00Comments on ?- true.: Haskell and the World: Unicode and the Common Misuse of ByteStringadimithttp://www.blogger.com/profile/04917371723395784281noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3460761117713509776.post-3086311465309540212012-04-30T13:59:59.939-07:002012-04-30T13:59:59.939-07:00Yes, tough in this post I was mostly concerned wit...Yes, tough in this post I was mostly concerned with textual data, for which Char8 is indeed the wrong tool.<br /><br />So my statement is maybe a bit drastic, but except in super-efficient stuff, it's probably still better to avoid it. JSON, for example, can contain variously encoded data, which would make usage of Char8 dangerous.adimithttps://www.blogger.com/profile/04917371723395784281noreply@blogger.comtag:blogger.com,1999:blog-3460761117713509776.post-81265978256637803442012-04-30T04:18:49.960-07:002012-04-30T04:18:49.960-07:00A valid use for ByteString.Char8 is for protocols ...A valid use for ByteString.Char8 is for protocols that require ASCII. It's no good for *human* text, but it does have a valid niche.Tweyhttp://www.twey.co.uk/noreply@blogger.com