We mention that ad scripts are a common type of problematic 3rd-party resource but we use the phrase “3rd-party resource” because there are lots of other common problematic scripts, like A/B tests, social media widgets, and analytics scripts.
How does Google works internally between teams on this kind of issues? For instance, do you work with people developing Google apps sometimes? Because it seems that they've gotten slower and slower as time goes: for instance, if YouTube was a porn tube, it will be dead already because it's much much slower than the competition.
This sort of basic advice (use browser features to defer loading, and plead with the masters not to ask for so much JavaScript) is obviously already considered by the HN audience and so this link is basically useless.
I sincerely doubt 100% of the HN audience always considers those things.
You might think some of those things are basic, but that doesn't make them useless.
This kind of lack of empathy for new learners can make it incredibly difficult to teach concepts to those who don't have as much knowledge as you may have.
We mention that ad scripts are a common type of problematic 3rd-party resource but we use the phrase “3rd-party resource” because there are lots of other common problematic scripts, like A/B tests, social media widgets, and analytics scripts.
Disclosure: I work on web.dev