[HN Gopher] Could we have avoided the whole UTF-16 fiasco? (2020)
       ___________________________________________________________________
        
       Could we have avoided the whole UTF-16 fiasco? (2020)
        
       Author : r721
       Score  : 18 points
       Date   : 2022-11-27 16:29 UTC (6 hours ago)
        
 (HTM) web link (retrocomputing.stackexchange.com)
 (TXT) w3m dump (retrocomputing.stackexchange.com)
        
       | nwellnhof wrote:
       | UTF-16 is not the only fiasco. Combining characters are mostly
       | useless overengineering as well, requiring composition,
       | decomposition and normalization forms and leading to exploits
       | like Zalgo text.
        
         | Someone wrote:
         | If it's _mostly_ useless, could we implement what it is needed
         | for in a simpler way?
         | 
         | If not, I wouldn't call it overengineering.
        
           | arcbyte wrote:
           | > "What is needed"
           | 
           | The best engineers do most of their engineering in the
           | requirements. Even if UTF16 is the only way to satisfy what
           | is wanted, is that really the best expression of what is
           | wanted or is it filled with misunderstandings and unnecessary
           | compromises? Almost always the latter.
        
       | baybal2 wrote:
        
       ___________________________________________________________________
       (page generated 2022-11-27 23:01 UTC)