he/him 
the first half of http://codemix.com/blog/why-babel-matters … is stellar. the second half kinda misses the point that babel isn't a long-term solution.
-
@sebmck because then you start blurring the lines between what the JIT should do and what the build step should do. Which i think is bad.
@helloandre You can be more lenient on your code and make certain assumptions that the JIT can't. Still always going to be the overhead…
-
-
@helloandre of allocating a function expression/closure for example. Your app likely won't care. JIT can't optimise that allocation away. -
@sebmck meh. i guess i'm just bucking against it because it isn't "standard practice" and mixing pre- and JIT- compiling seems inefficient. - 3 more replies
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.