I'm considering requiring file names to be UTF-8 on Sortix. Traditionally Unix allows any byte sequence (except '\0' and '/') in an unspecified encoding. This just creates problems. File names you can't type. Programming languages with UTF-16 strings can't access them.
-
Show this thread
-
It's nice, in a way, that the kernel doesn't care about the encoding. But it shifts the problem to user-space. Just today a bot broke at work because of a file name that wasn't UTF-8 and python just couldn't handle that. It's 2018, I can try and make everyone use a UTF-8 locale.
2 replies 0 retweets 3 likesShow this thread -
I'm also considering disallowing newlines in file names. I can't think of a good use. Their existence in file names is why some tools produce/consume \0 delimited records, but many tools just do newlines (especially portability). Forbidding them makes things a lot simpler.
3 replies 0 retweets 5 likesShow this thread
Yes, please do. I'd like to see more precedent for this.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.