search

ozten / TLD.js

Kickstarter project for applying for a JavaScript top level domain (.js TLD)
338 stars 37 forks source link

Extension of scope to code in all languages #42

Open joallard opened 12 years ago

joallard commented 12 years ago

I'd like to hear the community on this issue.

Would it be better to extend the TLD from JS to code in general?

As the .js is, in my opinion, never going to happen, some alternate TLDs have been proposed. (Issue #8, #40) TLDs like .app, .code, .src, apparently the leading contender at this point, don't really refer to Javascript any more but more like code projects in general.

Also, as Javascript developers often aren't really only JS devs but may also code say Ruby, Python, C, and so on.

Wouldn't it make more sense to extend the project to "projects who want to share their (open-source?) code or application"?

I guess the question comes down to whether there's enough place in the namespace to include those. I would think project names, across languages, are generally unique in the namespace. Try to think of a project name that collides with another in another programming language. There are surely some, but should we stop for those few exceptions? I think not. If we look at just .com, we can see how a namespace can contain many options.

In the end, I think the main issue that spurred that idea was this simple question: "Why would JS projects have a namespace, but other languages wouldn't?" Without wanting to raise a religion debate between the different languages out there, it does seem wasteful to me to potentially have each language community register a TLD, with the upfront costs that we know. So why not combine them and make just one TLD for the whole programming community?

beiju commented 12 years ago

I strongly agree with this proposition, though I want to mention that we need to think about how to approach other development communities. This idea has a lot of promise, but it could be easily derailed by even a small misstep in management. I don't want to see that. My suggestion is to get the other communities in on it as quickly as possible to avoid a culture where non-js developers are treated as second-class citizens, including and especially in the management committee.

As for my opinion on the specific TLD, I vote for the proposed system of {project}.{language}.src, with {language}.src as language-specific project listings.

sdepold commented 12 years ago

I would still like to have a .js tld. I guess it's kinda easy to get the js community formed around that tld. Way easier than getting people for a more general tld on board.

joallard commented 12 years ago

It would be nice, sure, but .js most-likely won't happen since 2-letter TLDs are reserved for countries (#8). Hence my interventions.

joallard commented 11 years ago

I forked the idea into a new project, .src.