I develop extensively in JavaScript, and this is fucking retarded.
Kickstarter for a JavaScript top level domain (.js TLD)
81–88 of 88 posts
Re: Kickstarter for a JavaScript top level domain (.js TLD)
#82I don't know why people are so eager to shoot this down. I think it's perfectly feasible. So what if two-letter TLDs are reserved for countries? JavaScript has already made the jump from the browser to the server (and, soon, to the kernel): the world map is the logical next step. Yes, I am talking about a real-world JavaScript nation, whose banner shall unite web 2.0 ninjas, wizards and pirates (not the rockstars, th…
Where on earth do you see JS jumping to the kernel? If C++ wasn't cut for it what makes you think JS is?
Yea I was thinking the same. The JavaScript nation thing was a bit far fetched but JavaScript in the kernel is simply absurd.
Re: Kickstarter for a JavaScript top level domain (.js TLD)
#83Re: Kickstarter for a JavaScript top level domain (.js TLD)
#84Re: Kickstarter for a JavaScript top level domain (.js TLD)
#85Re: Kickstarter for a JavaScript top level domain (.js TLD)
#86I tried doing this before the rules were public, the reasons why I stopped 1. Two-letter TLDs are reserved for countries. 2. The $200k isn't the actual cost, it is only what you need to pay for an initial review, you won't get the money back if something is found to be wrong with your application or if they dislike your TLD.
1. Except the .eu I guess (otherwise I agree).
Also .aq and a few islands that are part of bigger countries.
Those little exceptions don't invalidate the rule, and the request won't get accepted.
Re: Kickstarter for a JavaScript top level domain (.js TLD)
#87Why do we even think about this? Custom TLDs are a farce, a way to shake companies and nonprofits out of money without any added value, neither technologically, nor in terms of marketing/communication. Everybody knows that, right? Didn't we all conclude that when the ICANN announced it? Aren't "we", the hacker crowd, supposed to be above this?
You make a great ideological point sir. But let me make a pragmatic one. The new gTLD's are coming whether we like it or not, so why not take advantage of it?
Pragmatically speaking, the new gGTLDs are likely to fail. So why not avoid that expensive bullet?
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.
Re: Kickstarter for a JavaScript top level domain (.js TLD)
#88Earlier quoted context omitted.
You make a great ideological point sir. But let me make a pragmatic one. The new gTLD's are coming whether we like it or not, so why not take advantage of it?
Pragmatically speaking, the new gGTLDs are likely to fail. So why not avoid that expensive bullet? 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.
>Pragmatically speaking, the new gGTLDs are likely to fail. So why not avoid that expensive bullet?
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 ;).