Dear #nodejs community, the V8 team wants to work on making ES6/ES.next features competitive with their ES5 counterparts. 1/2
leading to commits like this: https://github.com/tildeio/glimmer/commit/83dd4498cfb03216bc22bedfbea96166e69c84db …
-
-
This probably captures the problem? https://bugs.chromium.org/p/v8/issues/detail?id=5456 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@github the problem is more about allocation tenuring + GC => very large deopts than the GC cost of the objs -
Yeah, we know that allocation pretenuring hurts easily in real world. We're working on that.
-
:) should help the ember problem ;)
-
Just checked back with the GC folks, they'll have another look. Rest assured, we got you covered! ;-)
End of conversation
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.