Hacker News new | ask | show | jobs
by ramones13 1248 days ago
I helped out with this post a bit - The examples he goes through are taken from actual performance investigations done on Microsoft apps that contributed to this feature being developed.

It’s not trying to say everyone should adopt those optimizations, but intended to be a hands-on “try it out” without the reader needing to have their own app handy :)

3 comments

Super! And thank you. I love this granularity of tooling now. it’s overwhelming, if anything.

To my original comment, I think I’m just naturally very wary of people losing themselves in the weeds without real cause. If there’s genuine slowdowns being experienced, absolutely dive into it. There are cautionary tales here though. Like when one makes an optimisation based on current browser implementations, only to have it be slower within a couple release cycles because the browsers have updated their implementations. Lots of this occurred with js looping idioms when es5 gained broader usage. All wasted time, in the end. IMHO it’s best to stick to idiomatic patterns and those espoused in the specs themselves. 99% of the time, that’ll cover you.

anytime we can stop the death by a thousand cuts is good news to begin to shape best practices and inform future choices. It's probably more the in aggregate threat than any single choice.
Is there any reason the blog post didn't have a link to the demo site?