> Not all communities seem able to do it, as in they can't even agree on which is the "least worst" (literally) of their choices.

The community should have the decision to keep their name as webapps.stackexchange.com

> When users see a Wikipedia link in their search results, they know what to expect. Hopefully when users see a stackexchange.com link they would also know to expect high quality Q&A. But what can they expect when they see nothingtoinstall.com or one of 25+ other domains? Unknown. 

Wikipedia is one community, the whole idea of stackexchange is to have a bunch of focused communities. If you wanted one community you'd have Yahoo! answers all over again. If you are designing for first rate communities then your members will be overall disjoint. If you are designing for second rate communities filled with only programmers then seeing .stackexchange.com is useful.

>Additionally, Google traffic makes up a HUGE percentage of our traffic and it hurts our Google ranking by breaking up into a series of top-level domains. That means less eyeballs, and ultimately less Q&A.

If this is really about page rank then wouldn't rolling stackoverflow into a .stackexchange.com really help out the page rank? Ditto serverfault and superuser? 

> The confusion that some people are talking about Web Apps while others are talking about "Nothing to Install". That will pass but become a bigger, more confusing problem as the network grows and we have (currently) 25+ different pairs of domain names to refer to!

Jeff posted a comment below which says that after a community gets to the size of serverfault then they will consider giving a name to that community. If you guys really had a concern here that comment shouldn't have been posted.

[1]: http://blog.stackoverflow.com/2010/07/the-7-essential-meta-questions-of-every-beta/