@domenic (I want to use this in prod) @lbljeffmo
-
-
Replying to @floydophone
@floydophone@lbljeffmo I think most everything is fast now but e.g. Iterators might be slower than for loops. /cc@ErikArvidsson1 reply 0 retweets 1 like -
Replying to @domenic
@domenic what about compilation speed? We've struggled a lot with that (on-the-fly) with JSTransform in node@floydophone@ErikArvidsson1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@floydophone@ErikArvidsson recent@stefanpenner benchmarks show it to be quite fast, and way faster than recast/esprima stuff2 replies 0 retweets 2 likes -
Replying to @domenic
@domenic recast is pretty slow but curious about the jstransform transforms (what we use in prod)@floydophone@ErikArvidsson@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@domenic@floydophone@erikarvidsson my tests show jstransform currently leading the pack2 replies 1 retweet 0 likes -
Replying to @stefanpenner
@lbljeffmo@domenic@floydophone@erikarvidsson esnext x 25.83 ops/sec traceur x 581 ops/sec 6to5 x 88.34 ops/sec jst x 3,443 ops/sec2 replies 1 retweet 1 like -
Replying to @stefanpenner
@stefanpenner@lbljeffmo@domenic@floydophone@erikarvidsson So many factors go into benchmarks that random numbers are pretty facetious.1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck yes, i welcome contributions to https://github.com/stefanpenner/basic-transpiler-benchmarks … to@lbljeffmo@domenic@floydophone@erikarvidsson1 reply 0 retweets 0 likes -
Replying to @stefanpenner
@stefanpenner@sebmck at variations like that, there's definitely some signal to be gleaned though@domenic@floydophone@ErikArvidsson1 reply 0 retweets 0 likes
@lbljeffmo @stefanpenner @domenic @floydophone @erikarvidsson Definently. 6to5 will always be slower due to the amount of static analysis.
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 