Actually it's kind of sad that it needs to be in C, most sane language would implement their server in themselves.

Why? Web Applications and Web Servers are two very different things with different language requirements. Seems sensible to pick the strongest languages with which to build the whole package.

I guess you don't push web servers. They're "apps", not system software. Anybody who deploys non-trivial web-apps knows this. Per-app web servers, standing behind a proxy, with a shared session-db is the most ideal way to get things done.

At this point in the game, Apache-class servers are glorified proxies, and occasionally dole out static data when you're not using a CDN.

I have customized my web server so much, I would've had to wait for years to see the changes in Apache, nginx or lighty, if ever.

Because most sane languages aren't just for writing web apps, they're for writing programs.