> Okay, this is kind of a vanity TLD, but we freaking build the web every day... Shouldn't we have a TLD that JS hackers control?
Why are "JS hackers" being targeted specifically? Why not also Ruby, Python, PHP, .NET, and Perl hackers? Why not also HTML and CSS hackers? Why not also designers (.psd perhaps)? Why not dozens of new TLDs so that everyone could have a domain with the file extension of their choosing?
I'll tell you why: because arbitrarily polluting the top-level namespace is something we learn not to do.
I guess .NET hackers are screwed though.
.dotnetLet's make custom TLDs for .py, .java, .c, .h, .php... really? Really?
The new gTLD's are coming whether we like it or not, so why not take advantage of it?
Aside: Has anyone ever run across a real functioning site that uses the .travel suffix? That is a precursor gTLD that went live in 2006. Presumably there are a lot more people interested in travel than there are in javascript.
If the premise is true, then I agree with the conclusion.
But what will make the new set of gTLD's likely to fail?
And what does "fail" mean even?
If all you are going on is history, not sure we can conclude anything. Past performance is a poor indicator of future performance.
If it weren't the case, then I switch professions and become a stock broker, because it would be dead simple that even I could understand it ;).