Anything you'd like to see performance improvements particularly? Except of course async/await and general Promise performance? 2/2
-
-
Replying to @bmeurer
Clemens Stolle Retweeted Sebastian Markbåge
objects as function arguments as mentioned in this threadhttps://twitter.com/sebmarkbage/status/783069272805220352 …
Clemens Stolle added,
1 reply 0 retweets 1 like -
Replying to @klaemo
Not sure what that means exactly. Can you give an example function?
1 reply 0 retweets 0 likes -
Replying to @bmeurer
the follow up tweets by
@sebmarkbage and@wycats outline the problem. I'm on my phone right now, can probably provide example later1 reply 0 retweets 0 likes -
We're aware of the Ember problem (in general). A simple example would be awesome tho.
2 replies 0 retweets 0 likes -
don't think there's 1 "ember problem"; we've probably significantly changed the profile since you last looked
1 reply 0 retweets 0 likes -
Glimmer doesn't look anything like ember internally and manifests the same issues with options objects.
1 reply 0 retweets 0 likes -
leading to commits like this: https://github.com/tildeio/glimmer/commit/83dd4498cfb03216bc22bedfbea96166e69c84db …
2 replies 0 retweets 0 likes -
@github the problem is more about allocation tenuring + GC => very large deopts than the GC cost of the objs2 replies 0 retweets 0 likes -
Yeah, we know that allocation pretenuring hurts easily in real world. We're working on that.
1 reply 0 retweets 0 likes
:) should help the ember problem ;)
-
-
Just checked back with the GC folks, they'll have another look. Rest assured, we got you covered! ;-)
0 replies 0 retweets 5 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.