@thejameskyle How so?
-
This Tweet is unavailable.
-
-
Replying to @jntrnr
@jntrnr You need to have specific tooling for linting, code coverage etc. It segregates the community and duplicates effort.@thejameskyle1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@thejameskyle sadly that'll be the problem with JS itself, TC39 revving the lang at a faster pace will cause lots of tooling probs2 replies 0 retweets 0 likes -
Replying to @jntrnr
@jntrnr@thejameskyle@geteslint is doing a remarkable job at supporting linting and gained complete ES6 in a very short amount of time.1 reply 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @jamiebuilds
@thejameskyle@sebmck@geteslint also, the JSX support is already going to cause bifurcation since it duplicates ES6 template strings1 reply 0 retweets 0 likes -
Replying to @jntrnr
@jntrnr@thejameskyle Disagree. JSX represents the specific semantics far easier. Seehttps://github.com/facebook/jsx#why-not-template-literals …1 reply 0 retweets 2 likes -
Replying to @sebmck
@sebmck@jntrnr@thejameskyle that link really doesn't make sense:P2 replies 0 retweets 0 likes
@stefanpenner Any specific parts? Seems pretty clear to me. @jntrnr @thejameskyle
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 