The greatness and limitations of the js-framework-benchmark 🔗
I love the js-framework-benchmark. It’s a true open-source success story – a shared benchmark, with contributions from various JavaScript framework au [...]
Read the Tea Leaves
Posts
Web components are okay 🔗
Every so often, the web development community gets into a tizzy about something, usually web components. I find these fights tiresome, but I also see [...]
Improving rendering performance with CSS content-visibility 🔗
Recently I got an interesting performance bug on emoji-picker-element: I’m on a fedi instance with 19k custom emojis […] and when I open the emoji pic [...]
The continuing tragedy of emoji on the web 🔗
Pop quiz: what emoji do you see below? [1] Depending on your browser and operating system, you might see: The flag of Martinique The old flag of Marti [...]
Reliable JavaScript benchmarking with Tachometer 🔗
Writing good benchmarks is hard. Even if you grasp the basics of performance timings and measurements, it’s easy to fool yourself: You weren’t measuri [...]
Is it okay to make connectedCallback async? 🔗
One question I see a lot about web components is whether this is okay: The answer is: yes. It’s fine. Go ahead and make your connectedCallbacks async. [...]
Bugs I’ve filed on browsers 🔗
I think filing bugs on browsers is one of the most useful things a web developer can do. When faced with a cross-browser compatibility problem, a lot [...]
Web component gotcha: constructor vs connectedCallback 🔗
A common mistake I see in web components is this: This setupLogic() can be just about anything – subscribing to a store, setting up event listeners, e [...]
2023 book review 🔗
Compared to previous years, my reading velocity has taken a bit of a nosedive. Blame videogames, maybe: I’ve put more hours into Civilization 6 than I [...]
Shadow DOM and the problem of encapsulation 🔗
Web components are kind of having a moment right now. And as part of that, shadow DOM is having a bit of a moment too. Or it would, except that much o [...]