4 ms·
> allows ambiguity between l and 1 It doesn't really. The canonical is L (uppercase). In practice lowercase l will never appear, unless for some reason you wan
by benatkin 6y ago
> allows ambiguity between l and 1
It doesn't really. The canonical is L (uppercase). In practice lowercase l will never appear, unless for some reason you want it to (you could convert L05ER to l05ER just for presentation, there are worse leetspeek offensive terms that would be allowed though).
Also the U/V thing neatly gets rid of FUCK. S/5 and I/1 take care of others.
- sedatk 6y agoI wouldn’t want ALLUPPERCASE identifiers on my URLs for instance. I presume that would be one of the most common scenarios it would be used in.
- benatkin 6y agoWell, it will still work but you'll lose the benefit of it. Most of these don't look like SHOUTING to me. They look uppercase but not aggressive.
- sedatk 6y agoYou don't want upper-case in URLs for social reasons. It simply looks out of place, takes more screen real-estate, and stands out unnecessarily. I'm just saying, if canonical is good enough, "S/5" fix isn't sufficient to get a whole new standard then. If it isn't good enough, then the value this one promises over Crockford is arguable due to lack of I/l/1 aliasing.
- deleted 6y ago[deleted]
- w-ll 6y agoI downcase all ids, sometimes this includes uuids and string ids.
- benatkin 6y agoThis is suggesting that you don't. It shouldn't be that hard to start using it in the canonical form - just start treating IDs as if they're case sensitive.