6to5 + esnext: Joining Forces https://6to5.org/blog/2015/01/12/6to5-esnext …
-
-
Replying to @babeljs
@6to5js@thejameskyle 6to5 feels like a problematic name since ES6 is not the end of the road for JavaScript ;)2 replies 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @jamiebuilds
@thejameskyle Long-term, +1 esnext if not a completely different name that still avoids confusion. ESNextTo5? :P@wycats2 replies 0 retweets 0 likes -
Replying to @addyosmani
@addyosmani Different name for sure. There's a naming conflict with esnext however as ES6 is also designated ES.next.@thejameskyle@wycats2 replies 0 retweets 0 likes -
Replying to @sebmck
@sebmck a more generic name in the same vein as the approach Traceur took?@thejameskyle@wycats3 replies 0 retweets 0 likes
Replying to @addyosmani
@addyosmani Yeah, that's defiantly the route that I'd like to go down. @thejameskyle @wycats
2:41 AM - 13 Jan 2015
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 