The Invisible JavaScript Backdoor
Listen guys, don't get me wrong. As someone with Ø in my name, and both Å and Ø in my address, don't get me started on poorly written systems which cannot handle unicode properly. I've seen my name and address mangled in shipping forms, in airline tickets (every time) and even in my marriage-papers since I married abroad.<p>I literally have <i>personal</i> reasons for getting everyone, and I mean everyone, on the unicode bandwagon.<p>That said... Maybe it's because I'm a child of the late 70s and early 80s and learned to program on computers which simply didn't have non-ASCII characters at all...<p>But can't we all just sit down and admit that allowing non-ASCII characters in programming-language identifiers was a bad idea? Can't we in the next revision of EcmaScript (or Rust, or whatever) mandate ASCII-only identifiers when in strict mode or using modules or whatever? Having <i>invisible characters</i> represent executable code is not just a dumb a idea, it's so hazardous that you might call it borderline malicious.<p>There <i>has</i> to be some way to undo this damage, without breaking compatibility with the code which is already out there, right?