>>27
What's so shitty about the FHS, I can find anything I want on the first try.
You still ask? Applications span over completely different directories the way you deal cards in multiplayer card games, you have shitty directories like /usr/bin where everything gets thrown in, can't tell what belongs to what, nor you can manage your applications by hand because it's fucking insane. On top of that it doesn't make any sense, has too many directories, has ridicule differentiations like /usr vs /usr/local, and many other issues.
If you don't compile things for Windows you are gay.
I compile things for Windows. My things.
Having to manually go search Google for binaries or source is a major pain though
It's even a worse pain to have to fix others' code or symlink some shitty library using that braindead library naming standard (OMG you have XXX 1.2.3, this required XXX 1.2.2, no run lol), just to try anything. You waste more time running configure, fixing crap and compiling than you do trying the actual software. It's so crappy to try stuff out, which is grave for an open sauce system/community with thousands of packages to try out.
I can't even imagine what I would do if I had to reinstall a Windows system from scratch. It'd probably take weeks.
Hi, ever tried copying stuff? It usually works as it is, because the directory structure is not shitty. In fact it's pretty much up to you. In the worst cases, you'll have to export and import portions of the registry. It takes two days at most.
Fixing things is not a waste of time
Yes, it is because these things shouldn't be broken from the start.
it might seem so to a Windows user though because as soon you manage to fix something, ten new problems will pop up.
That's because you failed it.
Case-sensitivity is sane.
Yes, because you speak with lowercase and uppercase, and you remember words with case. No, it's not sane, it's a pain in the ass, and it's very error prone. Why would you want to have a file named hippy and a different file named Hippy?
You seem to buy every crap Unix hippies throw at you. Now you're gonna say . should not be in the PATH because it's insecure, right?