Open jaydson opened 9 years ago
"harmonizr" is already taken by way too many projects. "Modern" and "future" are a bit too generic and don't convey much meaning imho.
"mcfly" is amusing and short, I like it the most from your list. But there's also a band called McFly and we could run into copyright issues.
I'm still considering something like "slush-babelrocks", because I really want to invest more into Babel and the "rocks" part has two meanings:
I'm pretty sure we can come up with better names than all of these, though. Let's keep the "temporarily definitive" es20xx name while we think and gather more feedback.
Hum..yeah, i don't know.
The slush-
prefix is being ignored?
I mean, why we can't use slush-harmonizr
?
It's a good invest on Babel, but babelrocks
seems to be a organization, not a project, IMHO.
I think the new name must to reflect what the tool do.
Let's keep thinking.
The
slush-
prefix is being ignored? I mean, why we can't useslush-harmonizr
?
Well, the slush-
prefix just means that the package is a Slush generator.
So, "slush-harmonizr" would read as "a Slush generator for projects using harmonizr".
This would be extremely confusing as there is actually a transpiler with that name and we are using a different transpiler.
It's a good invest on Babel, but babelrocks seems to be a organization, not a project, IMHO.
I hadn't seen from that point of view before, but I guess you're right.
Let's keep thinking.
:+1:
Random idea: slush-jsrocks
It is not very creative, but it is the workflow developed and used by @JSRocksHQ after all.
I guess we can come up with something more original, though.
Yeah, slush-jsrocks
seems like the best option until now.
Another random idea: slush-glimmer
Pros: kinda original, and this BuzzFeedJS tweet.
Cons: no real meaning.
slush-ladder
- stepping up your JavaScript game.
Okay, I'm not good with this naming stuff.
slush-babeltower
?
After all, this is a development stack based on Babel.
Though, the Tower of Babel story doesn't end too well and I don't particularly like religious references.
slush-babeling
?
Perhaps we could make use of the unused ideas in this issue.
That's a good idea.
slush-jarvis
sounds good to me, as in an AI copilot.
slush-sibyl
or slush-sibylla
also sound fairly good to me. From Greek Σιβυλλα (Sibylla), meaning "prophetess, sibyl" (ref).
Or we can remove the "es" part and leave it "20xx" (twenty double-x).
slush-babeller
?
slush-21st
slush-ultflow
, slush-rocksflow
Trivia: ultflow was a build tool proof of concept that I deprecated in favor of gulp before the first release.
rocksflow
= JSRocks + workflow. Okay, I tried.
rocksflow :+1:
After renaming, should we keep the version number or reset to 1.0.0? I guess it is less confusing to keep the version number, so users can just rename the dependency.
keep the version number, so users can just rename the dependency.
:+1:
I'm wondering whether we should wait until we add a front-end preset before we do the next major release with the rebranding. WDYT?
Hum, we can a plan a "big-awesome" release, with a new name and all the goodies.
I'll start working on a new JavaScript project which will support the browser environment, so I might start experimenting with Browserify in rocksflow soon. :smile_cat:
Cool! Let me know if you need anything
My suggestions: