3 ms·
Despite technical brilliance, this is one of the most closed-minded and stubborn crowds arounds. Just look at the reaction to adding case-insensitive functiona
by ClumsyPilot 6y ago
Despite technical brilliance, this is one of the most closed-minded and stubborn crowds arounds.
Just look at the reaction to adding case-insensitive functionality in filesystem in comments:
https://www.collabora.com/news-and-blog/blog/2020/08/27/using-the-linux-kernel-case-insensitive-feature-in-ext4/ https://www.collabora.com/news-and-blog/blog/2020/08/27/usin...
- swiley 6y agoCase insensitive filesystems are a really bad idea though.
- deleted 6y ago[deleted]
- colejohnson66 6y agoBut why? Why are they a bad idea besides “Windows does it and ‘Windows bad’”? Why is DNS case insensitive (example.com and EXAMPLE.com are the same), but not files (.Xauthority and .xauthority are different)? Case insensitivity lines up with the average user’s expectations. For example, if I’m searching for a file, I want a case insensitive match. Because if I named a file “Resume.txt” and searching “resume” didn’t bring it up, I’d be pretty confused. Now imagine the average Joe trying it. Explaining to them case sensitivity won’t convince them it’s a good idea because “Resume” and “resume” are the same thing.
- yakubin 6y agoShould that work different for different languages? Imagine the mess. Maybe the file names aren't even written in any human language. Should we use English rules for all languages? Why? What makes English so special that English characters would be normalized, but characters from the native language of the user won't? Wouldn't that trip people up? Case-insensitive file systems are mostly advocated for by those who only or mainly speak English and aren't aware of how much variety there is in the languages across the globe. And even in English "us" is a pronoun, whereas "US" is a country. EDIT: another question: should the normalization rules be changed when the language changes? Break backwards-compatibility?
- ClumsyPilot 6y agoThank you gor being exhibit A If you bothered reading the link, all of these questions have been addressed long ago by folks are are more knowledgeable than either one of us. The rules are spesific to each language, and are especially neccesary for languages thay have several alphabets. Without this functionality, efficient search is impossible. This silly, forcefull and uninformed critisism is exactly the kind of behaviour i was talking about.
- yakubin 6y agoI have bothered to read the link. The point of those questions wasn't to see if there are answers to them. The point of those questions was to show that all answers to them are flawed. Yes, the link provides one set of answers. (Except for the backwards-compatibility and changing language question.) But it doesn't solve the problem. When you want case-insensitive search, it's the search tool's job to provide it. E.g. whenever you want to do a case-insensitive search inside a file, you pass "-i" to grep or click a checkbox in a GUI. You don't change the file system to normalize characters inside files. From the link, it also seems like the main motivation for the change is compatibility with Windows software. In particular, it mentions that it isn't something that should be enabled globally in the file system. It really isn't a convenience for the user. The article makes a good case for providing compatibility with Windows software. But not for much else. Thank you gor being exhibit A
- ClumsyPilot 6y ago"The point of those questions was to show that all answers to them are flawed." Whats flawed? Where is it flawed? You provide no arguments at all! "When you want case-insensitive search, it's the search tool's job to provide it." I dont know if you didnt read it, or missed it, but the article clearlerly explains that the tool above the FS cannot do such a search performantly, it has to happen at the FS layer "You don't change the file system to normalize characters inside files." Where does this certainty come from? Why do you offer no technical argument to support your position? Is this by Pope's decree? Can you demonstrate a tool that can search efficiently in different alphabets, or when the same character is presentes by different unicode codepoints? Reading replies here convinces me even more that you just picked 'something something windows' and react like a bull does to a red rag. Not a single good technical counterargument has beed presented
- cweagans 6y agoIsn’t that an implementation detail of whatever tool you’re using for searching for files? I seem to remember most search utilities doing that already?
- IgorPartola 6y agoWhy would you ever want a case insensitive file system?
- detaro 6y agoClick the link.
- mixedCase 6y agoSo, for Windows compatibility layers.
- ClumsyPilot 6y agoSo you havent read 90% of the article about languages with mutiple alphabets or efficient search, but you are willing to argue anyway. Thanks for proving my point.
- mixedCase 6y agoI read it, even though you could be succintly making your points here instead of linking generic articles, and that's why I surfaced the only thing I considered valid. The usecase you bring up, including the multiple scripts issue, is search. And it's not and should not be a filesystem concern which optimizes for a different kind of access from which you can build search on top of.
- ClumsyPilot 6y agoThe article is not generic, it is spesific to the issue being discussed, and it explains the issue better than I can. "And it's not and should not be a filesystem concern which optimizes for a different kind of access" Why not? Is that by Pope's decree, or is there an actual reason for that? The filesystem already has like 3 different APIs, with and without caches, sync and async, so clearly they do optimise for different kinds of access. Can you demonstrate a tool that can search efficiently in different alphabets, or when the same character is presentes by different unicode codepoints?