What does bother me is that it’s called the World Wide Web and not the Worldwide Web.
What does bother me is that it’s called the World Wide Web and not the Worldwide Web.
E.g., it may not stop static.example.com from setting malicious cookies at the root.
It does. Subdomains can't set cookies for other subdomains. So long as you don't read root cookies, you'll be fine even if you do put static.example.com on some companies box that gets hacked without your knowledge.
However, outside of hacking (which is an issue no matter how you layout your domains), I can't think of a single problem with www-.
I wonder how many web apps are coded to reject cookies from a parent domain when they're expecting specific-subdomain cookies?
document.cookie in javascript just returns a string, and HTTP_COOKIE doesn't have any identifying information.
So yes, you're right. I was wrong. You can get poisoned by cookies on a root and there's really nothing you can do about it except hope that your browser is smart enough to make prefer your good.example.com cookies as opposed to the root cookies set by evil.example.com
Analogies always fail.
An internet[1] is to a continent as the Internet is to the Earth.
I agree that this argument[2] is thoroughly lost because people rarely use the capital 'I' anymore.
[1] You have all sorts of networks, but a network doesn't become 'an internet' just because it's using TCP/IP.
[2] Perhaps argument is too strong a word.
There are people in every generation who bemoan the “downfall” of language, and yet somehow I feel our languages get better over time, not worse—whatever that might mean.