5 ms·

jesus christ, who the fuck would make two identical symbols differentiated by only capitalisation? (Other than these guys obviously)

• lproven 9y ago
  What, you mean apart from every Unix ever? (All right, all right, excluding Mac OS X. But it's weird.)
  • kbody 9y ago
    There's a big difference between being and actually making use of such anti-patterns. Especially on such a scale.
  • jchw 9y ago
    That's filesystems, not the OS. There are some extremely good reasons to treat filenames as bags of bytes, which is why Apple got rid of case folding in APFS. Think performance, locale issues, etc. (And before someone says it, yes, of course performance matters for filenames. Every single stat shouldn't need to worry about case folding.)
    • deleted 9y ago
      [deleted]
  • 0x0 9y ago
    You can have macOS use case sensitive filesystems (like case sensitive HFS+), and you can have linux use a case insensitive file system (like FAT32)
• pjc50 9y ago
  It's surprising that most languages will happily let you do this. Lots of C programs have 'FOO' and 'foo'; not so many will have 'Foo' as well but it's probably more common than you think.
  • Laaas 9y ago
    IMO this is only a problem if they both are the same type, e.g. both are a function, both are a type, both are a variable, both are a special keyword, things like that, because then it's hard to mix them up. If however you can substitute one for the other in code and still have it compile, that would be terrible.
  • codedokode 9y ago
    It is humans' fault that they cannot choose good name for function, not languages'.