Skip to content

#frontend

3 posts on this topic, newest first. all tags →

How I turn any handful of colours into a readable theme

This site ships 18 hand-made themes and 368 base16 schemes. When I measured them, 16 of the first and all 368 of the second broke basic rules about contrast and colour. I wrote the rules down as code, built an engine that repairs a palette with the smallest change it can find, then pointed it at random colours. This is how it works and where it stops.

cssaccessibilitydesign-systems+2 more
17 min read20 min listen

Cache Components changed how I think about a page

Next.js 16 swapped the route level caching knobs for one directive, and 16.3 took it to the client for instant navigations. I migrated a content site and a dashboard. One got faster with almost no work. The other made me admit what a 'page' had been hiding the whole time.

nextjsreactcaching+1 more
9 min read11 min listen

I deleted every useMemo and nothing happened

The React Compiler is stable, on by default in new Next.js apps, and supposed to make most manual memoization redundant. I removed 212 useMemo and useCallback calls from a production app to see if that was true. It was, with four exceptions, and the exceptions show what those hooks were really doing.

reactperformancefrontend+1 more
8 min read10 min listen