he/him 
Making some progress on optimisations. Processing 2MB of JS:
@babeljs: 15.689s (Down from 30s)
Traceur: 2.563s
@typescriptlang: 2.909s
-
@sebmck@babeljs@typescriptlang why is traceur/ts so good? doing less?
@monasticpanic @babeljs @typescriptlang Different architectures mostly. Also Traceur/TS are written by teams of engineers… [1/2]
-
-
@monasticpanic@babeljs@typescriptlang who are intimately familiar with performant JS/compilers/VMs. [2/2] -
@sebmck@babeljs@typescriptlang makes sense. it is helps I've never thought babel was slow :) but the work is definately appreciated!
End of conversation
New conversation -
-
-
@sebmck@monasticpanic@babeljs : in the case of Traceur, "teams" ==@ErikArvidsson's 20% time. Yes, he's that good. -
@slightlylate@monasticpanic@babeljs@erikarvidsson You're also forgetting@johnjbarton :) - 1 more reply
New conversation -
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.