Rebranding?
UltCombo opened this issue · comments
Should we rebrand slush-es6 now that ECMAScript 6th edition has been renamed to ECMAScript 2015?
Some positive and negative ideas:
- es-2015 would look outdated too fast, so no.
- "es.next" is too damn overused all over the place, it is too generic so no.
- Perhaps "es20xx" or "es-20xx", then a JS logo with classic mega man would be quite suitable hahah.
Perhaps we can use some ideas from babel/babel#596 / babel/babel#568
@jaydson any ideas?
Guess I had too much free time so:
(I believe using a single sprite for parody purposes falls under fair use, and Capcom people usually isn't an ass regarding this)
I can't seem to find a good font to replace "JS" with "ES" though.
edit: crafted a quick and dirty "E":
edit2: just noticed I could borrow the "ES" from the ES Discuss logo:
Okay I should probably stop wasting time and get back to code.
Anyway, should we change the slush-es6 branding to something else? I believe this is the last step before publishing a stable release.
More suggestions:
- npm package name:
slush-es20xx; generator command:slush es20xx - npm package name:
slush-es-20xx; generator command:slush es-20xx
Not sure, but I feel like I should bet on the "20xx" idea. If we have copyright problems in the future, we can as well just remove the sprite and keep the "20xx" as a subtle reference.
Now with less blurry sprites (got originals and resized using nearest neighbor interpolation), and damn, how I could I forget about the Rush Adapter:
Btw, all images posted above are Adobe Fireworks PNGs in case anyone want to work on them.
Now with not only the "20xx" reference, but also the Rush Adapter representing code transformation and improvement, I'm certain that MM7 will be the mascot for slush-es20xx.
Sorry for let you speaking with yourself 😢
I just loved the "es20xx" idea.
Perhaps we can use try something like this on ES6Rocks.com ?
Let's think about it.
Hahah no problem. I like discussing with myself sometimes.
As for the ES6Rocks.com branding, we can bring it up in the appropriate issue, yes.