Might depend on your file browser.
You may also want to try, for example, the files “a1”, “a2”, “a3”, and “a10”. Lexicographically, “a2”>“a10”, but my file browser displays “a10” after “a2”.
Might depend on your file browser.
You may also want to try, for example, the files “a1”, “a2”, “a3”, and “a10”. Lexicographically, “a2”>“a10”, but my file browser displays “a10” after “a2”.
Think the other way around: What’s the use case for case insensitive file names? Does it justify the effort and complexity for the filesystem and the programs to know the difference between lower and upper space chars?
I agree. It’s also interesting how the hair thing has a skull (see 2nd panel).
But there is of course room for improvement. If you look at the window for example, it has a nice normal modern handle, but it’s blatantly missing the window sill and the hinges. :)
That’s not football, it’s soccer.
Regular expressions in general, and automata theory, sure you should know about that. But a specific extended regex language like here? That’s like saying you’re shit at coding if you can’t do <insert arbitrary programming language here>.
People, corporations, and other entities would over time gather more data about you. There’s always some kind of information footprint that you leave behind. And you’d stand out from other humans by the way you talk (i.e. using slang from 200 years ago, and speaking about historic stuff with details that the general public is not aware of) and other traits, which makes you traceable.
You’d procrastinate things for 100s of years, until at one point you’re simply no longer able to do it. Wanted to domesticate a saber-tooth cat some day? Too bad, they’re extinct now. Wanted to visit the baths in ancient Rome? Well, it is not the same Rome anymore, and all the baths’ floors are cold.
I didn’t know penguins could marry.
Or make your window very flat, so the DVD always bounces.