> Unstable, as in needs to be rebooted after most patches. OS X is in the same boat.
> Unstable, as in needs to be rebooted about one a week just to clear > the memory leaks (I "grew up" with uptimes measured in months, and in > one case, years, not days). This was true for NT and pre-2000 clients, but that's ancient history. What are you doing now to require this? I have systems that run for months with no ill effects. > Unstable, as in two server side applications can not be run > simultaneously without figuring out where all the conflicts will be > first. This is simply not true. I won't say that conflicts don't happen, but only under certain conditions. This is not something I worry about too much. > Unstable, as in because of the above spawned a new industry to take > advantage of the fact that most Windows servers are at trivial > utilization. I'm not sure what you mean by this. > Unstable, as in its freaking mail program and browser was able to > directly access the kernel. No argument there. ************************************************************************* ** List info, subscription management, list rules, archives, privacy ** ** policy, calmness, a member map, and more at http://www.cguys.org/ ** *************************************************************************
