Post

NullVoxPopuli
@nullvoxpopuli.com

For a long while, ~ I've felt no benchmark (that I know of) has captured the relationship between ~ reactivity and rendering We have rendering benchmarks. We have reactivity benchmarks. I had to make my own. I did not expect these results

NullVoxPopuli
@nullvoxpopuli.com

(So that I can improve Ember, ofc) To my surprise, Angular is leading ahead of everyone. *By far*. Impressive stuff, Angular team! Seriously! absolute nutso!

NullVoxPopuli
@nullvoxpopuli.com

Anyone and everyone is welcome to challenge me on these benchmarks -- I haven't intended it to be a super serious community tool or anything, but I just wanted to celebrate the Angular team's hard work on getting the perf balance this tight.

0 reposts5 likes

NullVoxPopuli
@nullvoxpopuli.com

I started all of this as way to improve the *real world* experience of ember apps, as _applications_ have more updates than rendering tables (tho, I'm keen on improving that as well) I have a spike which dramatically improves things here for Ember as well:

NullVoxPopuli
@nullvoxpopuli.com

it turns out that a *lot* of these perf improvements are due to when you decide to touch the DOM -- the responsibility of the "Scheduler" So I think with perhaps a couple tweaks to however Solid renders, they could also get massive score boost here