I have no idea why @ChromeDevTools have only x4/x6 CPU Throttling settings, but my M1 Mac is too damn fast to cause long tasks even with x6.
It was so annoying that I developed a little extension for this. Still a little buggy but does the job🤘.
And now it’s riddle time! What will the following code print and when will the DOM change be actually painted to the screen?
Bonus question: what will change (if anything at all) if you resolve the promise in 30ms instead of 10ms?
This alone was worth all the time I spent on this article.
1. If you enjoy someone's work - let them know, it's really incentivizing.
2. If you didn't read the article - give it a go, you might learn a few things about #webperf, #javascript and #webpack.
Love the statement 😅.
A nice read by @DebugBear on how @____lighthouse simulated network throttling compares to @ChromeDevTools and system-level throttling:
https://www.debugbear.com/blog/network-throttling-methods.