It's the tribal nature of Man. You want to nail you colours to the mast of the chosen tribe and posture with the perceived strengths you have over the others.
Sitting in the middle of a dark empty room and focusing until you're able to move the kundalini energy from the base of your spine to your brain, which will allow you to manipulate the energy of the void and instantly manifest anything you want. ^_^
helios, I thought you would have noticed that it was a joke lol. I didn't mean it seriously at all. But the theory and reason on why it is that way still applies. The idea of compile-time optimization and configuration isn't bad in my opinion. But remember that some Windows applications often use a lot more dependencies. For instance, open up one of these Windows-specific apps' that claim to be mature and you'll find 20+ DLLs sprawled all over the place having different and obscure names that make you sometimes say wtf. That rarely happens on Linux now adays and they try and use common libraries for everyone to use for cleanliness and organization. Just because compilation is an effort, you'll often find yourself having to find if you have a common library which more often than not, you'll already have because of the dependency of another application you needed to install it for. The situation for compatibility hell is no more dangerous on Linux than it is on Windows or any others. In this case, your complaining about compiling itself because of the difficulty to grab all of the dependencies. You still have to do that on Windows and almost all Linux package managers will provide a stable development release for the package you are looking for where as Windows does not.
But remember that some Windows applications often use a lot more dependencies. For instance, open up one of these Windows-specific apps' that claim to be mature and you'll find 20+ DLLs sprawled all over the place having different and obscure names that make you sometimes say wtf.
Yes, but there's a very important difference. Binary compatibility allows the developer to bundle dependencies with the program. Sure, it introduces redundancy into the system, but it's not like storage is that expensive nowadays. It also prevents DLL Hell. By providing the library the program was designed for, system-wide updates don't affect its operation.
obscure names
Don't get me started on typical UNIX library names.
libxmlrpc_xmltok.so.3.6.15
grab all of the dependencies. You still have to do that on Windows
LOL. Yeah, I can totally remember when I had to fetch over 9000 DLLs when I tried to run Visual Studio. Come on, dude. Seriously.
I'm pretty sure he meant tracking down dependencies for programs you compile yourself. I don't remember the last time I had to compile Visual Studio from source.
I'm pretty sure he meant tracking down dependencies for programs you compile yourself.
In that case, getting dependencies for compilation under Linux is so easy only because of how unnaturally common it is to compile programs.
Try this experiment: make a statistic of how many non-programmer users have a compiler of any kind installed in their system, discriminating by operating system.
I guess some people are just so used to windows it's hard to get used to other operating systems. It's like inertia or something.
Try this experiment: make a statistic of how many non-programmer users have a compiler of any kind installed in their system, discriminating by operating system.
Every UNIX-like system I've used (Linux, FreeBSD, MINIX, OpenSolaris) and all the others that I know of come with gcc pre-installed.
Stockholm syndrome is a psychological response sometimes seen in abducted hostages, in which the hostage shows signs of loyalty to the hostage-taker, regardless of the danger or risk in which they have been placed.
<sadMac>
ERROR: but rather than tell you anything useful about the problem (like Linux's "panic" screen or even windows' BSOD), I'll just show you this pretty picture.
</sadMac>
Which reminds me... the guys at the apple store near where I live are so easy to troll; I once downloaded a picture of a Linux kernel panic screen, put it in MS powerpoint and made it go fullscreen... and they thought it was actually broken (without noticing that it had "linux" on the screen in several places).
Oooh... that was a cruel practical joke. But on a more important note, one problem I have with Mac OS X is that is so "perfect" for everyone that few ever have to learn about how it works, and therefore when it breaks, they're stuck more than a Windows user would be. It doesn't help that all the useful system files are hidden and that the error screen is fairly... um... uncommunicative.