New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Name suggestions #596
Comments
I think I'm partial to the "random" names; rosette and babel, in particular. |
👍 |
Babel could actually be a good one — it translates all this cutting edge JS into a common language. |
I like Rosetta and Babel because they both have origins in language translation which links back to the actual goals of 6to5. |
How about Babel fish?
in memory of Douglas Adams also: |
👍 to babel (or babel fish), "Rosetta" is fairly well established for other commercial products. |
Only problem is that I sound ridiculous saying "babel" with an Australian accent. |
I'm now convinced this is the best name for the project. |
I like babel. |
You can shorten it to just bab. /hipster |
👍 to babel, babeljs, jsnext, or nextjs. |
If 6to5 is gonna have transformers for profiling, optimization, minification, etc as hinted in the future scope thread, then names like "js.next" don't really capture the full spirit of the project imo what about a name like "JSworks" or "JSkit" |
"JSnext" is good but shares a name with a conference and is similar to "nextJS" (also extant). Of course, the inadequacy of "6to5" isn't just in the fact that ES6 isn't indicative of the target implementation, but the fact that ES5 isn't even the target environment (in the near future I might be using this to compile to ES6 or — suspend your disbelief — someone might extend the project to work in IE7 ;). How about "next2now"? I think that sums up the general spirit without being too limited in scope or recondite (who wants this to be associated with Altavista's automated translation service?). |
I like babel. I'm strongly against I'm not saying you shouldn't use a name because some ethnicity objects, just saying it'll feel weird to me, and probably other german speakers 😂 |
@despairblue Well it's gotta come out somewhere right? 😄 Throwing another suggestion to the pool: milljs |
BackToTheFuture.js 😄 |
IMO we should avoid js postfix |
@dashed true, but I feel that 6to5 does not produce crap, quite the contrary 😉 |
|
sounds hard to google for though :P |
The name I used for 6to5 before I publicly released it was actually delorean 😜 |
delorean is now a flux thing http://deloreanjs.com/ |
@dashed Seems like everyone and their dog has their own flux implementation. |
Good to know we are on the same wave :D |
@chicoxyzzy Every simple name will probably be taken by some obscure library. |
My two cents, should try to avoid things that already exist in the not only npm registry, but also the unix ecosystem. Prime example of this is |
And a mandatory random suggestion |
TV/movie-inspired names:
More names:
|
Throwing a few more:
P.S. +1 for |
Xtojs? |
adaptable |
Concord is taken: https://github.com/webpack/concord |
Can I put in a vote for leaving it as Or... what about If you do change it, |
@developit See #568, regarding the project future and scope. I'm not comfortable with the name and nothing is really going to change that. The current ES target is as low as we can reliastically make it (in a lot of cases ES3) and we already support some ES7 features so the name is already completely wrong without having to stretch the project scope at all. Having a conflicting name is bizarre and doesn't make me feel good about the projects longevity. |
Ah, hence the |
2js? |
ECMAswitch |
JS |
|
Harmonizr |
@jaydson nice idea, but a transpiler with that name already exists https://github.com/jdiamond/harmonizr |
:/ |
I like Continuum and Harmonizr the best. I understand there are projects with these names already, but they have been abandoned. How about we ping the developers of those projects and ask for their opinions? |
@elclanrs IMO repurposing existing project names is rather confusing for those who have already heard of that project, plus those who search for resources would find stuff regarding the past project by the same name which is extra confusing. |
Inspired by this comment, why not just call it x? |
Then we could all ask others to "x 'ma script" (sorry) |
I know that you think that 6to5 holds a certain connotation towards "converting ES 6 to ES 5" and that somehow hinders your ability to do more. But the name isn't "ES6toES5". The numbers 6 and 5 can mean anything you want them to, and be as generic as the name switch. To me it means being able to stop working a 5 PM instead of 6 AM. ... Although not recently..., but still, saves me a ton of time! My point is it's a name. And while the to-do list for changing the name is involved, you also have to consider developers updating their dependencies as well. And you're already well established with the name, it's short, and hard to confuse or misspell. For some reason when I think of 6to5 I think of a clock. If you must change it, the suggestion I'll throw out is "fin", seen as "the end" seen in old films. |
Thanks everyone for your suggestions! Possibly leaning more towards what @lukescott said. I'll have to deliberate and decide. Again, thank you everyone! |
|
esnext2015to5(Over my dead body)20xxDowncastThe text was updated successfully, but these errors were encountered: