▲ 1416 ▼ D or d come on (i.imgur.com) submitted 2 years ago by genfood@feddit.de to c/programmer_humor@programming.dev 221 comments fedilink hide all child comments
[–] Honytawk@lemmy.zip 11 points 2 years ago (5 children) Why would case sensitive path names be considered dangerous? permalink fedilink source parent hideshow 5 child comments replies: [–] colonial@lemmy.world 12 points 2 years ago* (3 children) I don't know about dangerous, but case-insensitive Unicode comparison is annoying, expensive and probably prone to footguns compared to a simple byte-for-byte equality check. Obviously, it can be done, but I guess Linux devs don't consider it worthwhile. (And yes, all modern filesystems support Unicode. Linux stores them as arbitrary bytes, Apple's HFS uses... some special bullshit, and Windows uses UTF-16.) permalink fedilink source parent hideshow 3 child comments replies: [–] MenacingPerson@lemm.ee 1 point 2 years ago Meanwhile fishshell: permalink fedilink source parent [–] lnee@lemm.ee 1 point 2 years ago (1 child) so if linux stores file names as arbitrary bytes them could I modify a ext4 fs to include a / in a file name permalink fedilink source parent hideshow 1 child comment replies: [–] kattfisk@lemmy.dbzer0.com 1 point 2 years ago If you did it would likely break something as it's one of only two characters not allowed in a file name (the other being null). You can do a lot of funky stuff within the rules though, think about control characters, non-printing characters, newlines, homographs, emojis etc. and go forth and make your file system chaos! permalink fedilink source parent [+] MonkderZweite@feddit.ch 1 point 2 years ago [deleted] permalink fedilink source parent
[–] colonial@lemmy.world 12 points 2 years ago* (3 children) I don't know about dangerous, but case-insensitive Unicode comparison is annoying, expensive and probably prone to footguns compared to a simple byte-for-byte equality check. Obviously, it can be done, but I guess Linux devs don't consider it worthwhile. (And yes, all modern filesystems support Unicode. Linux stores them as arbitrary bytes, Apple's HFS uses... some special bullshit, and Windows uses UTF-16.) permalink fedilink source parent hideshow 3 child comments replies: [–] MenacingPerson@lemm.ee 1 point 2 years ago Meanwhile fishshell: permalink fedilink source parent [–] lnee@lemm.ee 1 point 2 years ago (1 child) so if linux stores file names as arbitrary bytes them could I modify a ext4 fs to include a / in a file name permalink fedilink source parent hideshow 1 child comment replies: [–] kattfisk@lemmy.dbzer0.com 1 point 2 years ago If you did it would likely break something as it's one of only two characters not allowed in a file name (the other being null). You can do a lot of funky stuff within the rules though, think about control characters, non-printing characters, newlines, homographs, emojis etc. and go forth and make your file system chaos! permalink fedilink source parent
[–] lnee@lemm.ee 1 point 2 years ago (1 child) so if linux stores file names as arbitrary bytes them could I modify a ext4 fs to include a / in a file name permalink fedilink source parent hideshow 1 child comment replies: [–] kattfisk@lemmy.dbzer0.com 1 point 2 years ago If you did it would likely break something as it's one of only two characters not allowed in a file name (the other being null). You can do a lot of funky stuff within the rules though, think about control characters, non-printing characters, newlines, homographs, emojis etc. and go forth and make your file system chaos! permalink fedilink source parent
[–] kattfisk@lemmy.dbzer0.com 1 point 2 years ago If you did it would likely break something as it's one of only two characters not allowed in a file name (the other being null). You can do a lot of funky stuff within the rules though, think about control characters, non-printing characters, newlines, homographs, emojis etc. and go forth and make your file system chaos! permalink fedilink source parent