It is, but bear in mind many companies have different architectures or even hosts behind their blogs vs their main site (or even product). For example, a Rails or Django app for the main site, PHP/Tumblr/Wordpress.com for the blog.

There are some proxying shenanigans you can do with mod_rewrite but I'd certainly not want a PHP-based blog anywhere near my main site/app if I could get away with it due to the security risks.

That's pretty trivial to do with nginx though, isn't it? I have a server that can run php on certain subdomains AND folders, node.js on others and I suppose ruby would be pretty easy too.

In fact, on one domain nginx sends part of the traffice /static/ directly to that actual directory, and anything else gets picked up by node.js.

Or is what I'm doing really stupid? I'm not currently running anything significant on my servers, and this is not my primary domain of interest, so I've never checked how risky my setup is. Maybe you could tell me if that's the case?

Dharmesh had mentioned it really wasn't that big of a difference either way. Personally I have no idea outside of a short exchange with him about it.

I didn't know that. Thanks for that heads up.