Can we, as framework authors, do a better job of communicating which personas are appropriate for our frameworks, using quantitative measures that the community agrees on broadly?
These techniques have different tradeoffs depending on how expensive network is vs. CPU. And sometimes expensive means literal money.
-
-
These are all the questions I could use data on more than "how many bytes is a React hello world" as we work on the next iteration of Ember tooling.
-
Yep, definitely some good things to study here. Some are thinks we're starting to track and expose more seriously in the browser - like overall input latency metrics. Also we're studying the effect of lazy loading iframes and images, so that's a related piece...
-
But it sounds like a lot of what you're talking about is experimenting with frameworks and measuring at that level. Eg. I don't think we can automatically detect spinners in a generic way. Maybe a need for some co-ordination APIs though?
-
I'm hoping that in addition to First Input Delay, we'll get Worst Input Delay into the CrUX report. That should help capture some of what you're talking about. But custom telemetry from framework code seems strictly superior to me...
-
I'd be very interested in collaborating on this and adding support to Ember for anything we come up with.
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.