Ryan Townsend (old account)

464 Followers
168 Following
1,033 Posts

Another screenshot for my "we [as an industry] can do better" folder... scrolling down on a Forbes article consistently bricks the page.

*checks console* yup, it's *that* JS framework.

It's a fucking static article 🤦‍♂️

Back in my happy place 😌

This is the last photo I took of him, after we’d put him to sleep.

As he went calmly, I cradled his head while Rosie stroked him and we told him how much he was loved by all.

We made a pillow from an old tee of mine he used to sleep on in my wardrobe and an old pyjama top of Rosie’s as a blanket.

Farewell, our little prince.

Fuck cancer.

My little family has been torn apart.

Our cat Ivan had to be put to sleep on Friday.

We are blindsided – he’d had a little cough for a couple of weeks which was believed to be asthma or maybe pneumonia, but it turned out he had an aggressive lung cancer and deteriorated quickly.

We (as an industry) cross-browser test down to as little as 1% browser adoption, we A/B test to eek-out fractional improvements… so why aren’t we monitoring down to the worst 1% of interactions?!

@anniesullie explains the Core Web Vital 75th percentile threshold is just the starting point 👏🏻

#perfnow #webperf

An exciting new timing API from the Bloomberg team: https://github.com/bloomberg/container-timing 🎉

#perfnow #webperf

GitHub - bloomberg/container-timing: Container Timing

Container Timing. Contribute to bloomberg/container-timing development by creating an account on GitHub.

GitHub
PSA: please please please upvote and show interest in https://github.com/whatwg/dom/issues/1308 and we’ll have easily deployable, non-hacky solution for yielding on interactions – then we can all see these gains demonstrated by @erwin at #perfnow
Proposal: asynchronous event listeners · Issue #1308 · whatwg/dom

What is the issue with the DOM Standard? I've heard chatterings in a few different places about interest in asynchronous event listeners on the platform, so I figured I'd file a bug here for some m...

GitHub
Fascinating breakdown of devices used by the typically very privileged #perfnow audience… a huge volume of fairly new iPhones, of course, but still many lower-powered devices.

A common misconception by web developers is that webfonts will download once they’re discovered in CSS, but the browser will actually only download them once there’s a DOM node actually wanting to use a given webfont.

Glad @mandymichael cleared this up at #perfnow 🎉 #webperf

Something I’d never considered: narrowing the range of axis within variable fonts to remove unused extremes will reduce the file size!

@mandymichael at #perfnow #webperf