I don't think anyone could argue that having skills in both areas isn't a good thing. I've been a sysadmin for 20 years and i've had to do basic development over the years (apache modules, ldap-ifying applications, etc). When it comes to troubleshooting complex problems as a sysadmin and the whole team is whiteboarding, you can tell pretty quickly who understands how systems work below the user interface. This is often only learned through writing code.

The opposite is true for coders too. With a few execeptions, the most competent developers I've worked with have had sysadmin duties at some point in their career. Not that long ago, I had to sit down with a Sr. (Java) developer and explain load balancers and TCP session state.

I understand that wikipedia is a non-profit and has limited resources, but why not just do it? This doesn't seem like a radical stance at all. This should be on their roadmap. Given wikipedia history of taking sides on issues like this, they should be pioneers in doing this sort of thing.

Plain text HTTP is on its way to becoming a legacy protocol.

I couldn't agree more. I've never experienced support like we get from MS. Just recently we had a 12GB .dmp file analyzed and in less than 36 hours they were able to tell us which shitty 3rd party driver was causing our boxes to BSOD. The vendor that shipped this driver (mentioned in the parent above) is so far, completely useless.

"Judge Gerald Bruce Lee of U.S. District Court for the Eastern District of Virginia [...] also stripped Zhao, from China, of her U.S. citizenship"

What the hell? I was unaware that there are different classes of citizenship. What if a person born as an American did this?