I must disagree. with both sides.
Autoconfiguration is better because the package maintainers
know which options are less secure and can configure it
safely. There are numerous tools that check code for
potential buffer overflows and unsafe practices. Eric S
Raymod said it best: With enough eyes, all bugs are
shallow. Second: Maintainers are encouraged to go back and
fix bugs simply because what they create "scratches their
own itch." What they make they have pressing need for.
Microsoft, while no doubt they use their own products,
don't fix bugs as often. Linux maintainers fix bugs and
holes as soon as possible, because, to a person, their bugs
and holes leave themselves open to attack just the same as
the little guy. the learning curve for configuration can be
a good thing: it encourages people to read the
documentation, ask for help, and "Do the Right Thing." Best
practices without a central authority. The fact that
there's more than one way to do something (IE: you can use
xwindows, xfree, or even no WM at all, firefox, mozilla,
netscape, or even lynx/links for no pictures, for web
browsing, different versions of kernel modules that might
or might not have a feature spyware has, even down to the
equivalent of a windows print spooler.) means diversity.
And we all learned about diversity and evolution.
Stagnation and lack of diversity encourages infections and
can end up killing the entire population of an organism
(Dutch elm disease is a good example. As is diseases
involving vinyards) Windows autoconfigures to a degree
also, so your arguement is somewhat disengenuous. Also, I
don't think IBM and Oracle would get behind Linux if it
wasn't a smart idea.
On the other hand, Linux can be a pain to configure
(network sharing, for example. my firewall would be Linux
but for the fact that I needed something "now" and you
can't get much more 'now' than installing windows, clicking
7 times, typing some data in and pressing OK.
If Linux did become the dominant OS, I agree that there
might be more discovered bugs, but most linux distributions
have the equivalent of windows update and some even have
the equivalent of auto-update.
Windows is great for users who just want something to check
E-mail and play games, Linux operates well as a server OS.
Nothing wong with that. At the risk of pissing off MSFT I'd
like to remind about the teething issues of transferring
Hotmail from *nix (*BSD) to windows.
Use whatever works, but in the realm of security and
usability for highly technical applications, I'd have to
lean towards Linux. Average linux users are more
knowledgable and can help you to do what you are trying to
do, and the software is generally more featureful without
being bloated (emacs aside). You can get ahold of the
maintainers of whatever isn't working and most can help you
with a patch or updated version nearly immediately.
Besides, How can Microsoft compete with something that'll
scale from a 386 with 4mb ram (most distros. For embedded
systems, even less) to your latest Pentium 4 3.2ghz with
over a gig of ram. (Trust me, I've transferred a HD with
linux on it to a box where the main drive got corrupted to
the point that most recovery tools gave up, completely
different processor and speed, recovered the data off of
the drive, and replaced it on a replacement drive exactly
as before, shut down, pulled my drive and restarted, and
the system booted as normal. The user was quite impressed.
I'd like to see XP/2k do that without complaining. The OS
on the disk thought: "Okay, let's see, what do we need to
load to operate, load this that and the other, okay, we're
good, let's show the login screen. good." it does this for
all systems and hardware. Like I said, use what works, but
I lean towards linux.