@thejameskyle @BrendanEich *much* less spec-compliant though, I would not recommend because of forward-incompat hazards.
-
This Tweet is unavailable.
-
-
Replying to @domenic
@domenic@thejameskyle@BrendanEich really, 6to5 much less spec-compliant? Dang, I was way more drawn to it than to Traceur… Any ref info?1 reply 0 retweets 0 likes -
Replying to @porteneuve
@porteneuve@domenic@thejameskyle@brendaneich 6to5 is more spec compliant than Traceur. Extremely curious to hear why you think otherwise.1 reply 0 retweets 1 like -
Replying to @sebmck
@sebmck@porteneuve@thejameskyle@BrendanEich The focus on readability of generated code causes major deviances from the spec.1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@porteneuve@thejameskyle@brendaneich Heavily disagree. 6to5 has higher compat-table https://kangax.github.io/compat-table/es6/ … among other things.1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@porteneuve@thejameskyle@BrendanEich compat-table tests are shallow. But e.g. array comprehensions are hiliariously wrong.3 replies 0 retweets 0 likes -
Replying to @domenic
@sebmck@porteneuve@thejameskyle@BrendanEich see also: method definitions, destructuring of iterables, ...4 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@porteneuve@thejameskyle@brendaneich As of 2.0.4 I've fixed destructuring iterables being too greedy. Happy to fix anything else.1 reply 0 retweets 1 like -
Replying to @sebmck
@sebmck@porteneuve@thejameskyle@BrendanEich I guess I should change my tune, if compliance is indeed a goal. Seemed like it wasn't.1 reply 0 retweets 0 likes
@domenic @porteneuve @thejameskyle @brendaneich It definently is. Readability is a big goal but I'm not willing to sacrifice spec compliancy
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 