I can not tell you, how much I thought the same. It sounds like an answer filled with as many buzzwords you can think of, made up by some random as a joke, moking such answers. Then I saw the username highlighted in blue, indicating it was OP.
I am still not sure of it’s just a mocking answer, tbh.
As someone working as on-site IT support for over 15 years, I can’t tell you how often I have asked people to restart their computer over the phone and they swore they did (“multiple times even”), only for me to eventually come around to their desk and having them actually reboot the device in my presence and for the problem to actually fix itself.
One Lady I asked to restart their computer said “all right, hold on.” only to respond not even 10 seconds (!) later "I did, its still not working„ and after the third time I went to her desk and asked her to show me what she did. She leaned forward, turned off the monitor, then turned it back on. “I did this 10 times already, and its still not working”.
Some people just lie about rebooting, some simply don’t actually know how to reboot properly. After a few months, you get to know who’s lying, who’s doesn’t know better and who’s actually telling you the truth, you get to know your coworkers.
You can call them “communities” if you want, but it’s longer and can’t easily be shortened.
I propose “commies”
There’s always an xkcd:
From a technical standpoint, the windows NTFS filesystem is designed inherently case sensitive, just windows doesn’t allow creating case sensitive files.
Connecting an NTFS drive to linux, you can create two separate files readme.txt and Readme.txt.
Using windows, you can see both files in the filesystem, but chances are most (if not all) software will struggle accessing both files, opening readme.txt might instead open Readme.txt or vice versa.