I find this fun and whimsical, but surely it’s an accessibility nightmare.

No difference from using a div/span.

simply only ever use this to replace <span> or <div>

aria tags for days

Yes, the hydration behavior of custom elements is nice. You don’t even need to do anything special with JS bundle loading.

Simply render your <element> (server-side is fine) and whenever the JavaScript downloads and executes your custom elements will mount and do their thing.

I love the transaction history in YNAB. I refer to it all the time.

Costco membership is more like voluntarily accepting cookies.

Even more than that, it’s purchasing a membership that requires authentication when you use the store.

Crazy. I switch between my work’s M4 MacBook Pro and my personal M3 MacBook Air all the time and I forget that the displays are even different.

I can’t imagine not rinsing after brushing, with your mouth full of toothpaste

You need to configure it for static export if that’s what you want: https://nextjs.org/docs/app/guides/static-exports

But this won’t support all framework features. The default expectation for Next.js is with a server runtime for SSR.

They should just do something like have parental controls that can configure the user agent with the user’s age, and require adult websites to not serve underage users.

It wouldn’t deter kids if you want to let them have unsupervised root access to a computer (like I enjoyed when I was 12), but I think it would be fairly effective for a walled garden like an iPhone

It’s been a long time since I used it but an iOS subsonic client I used to use (I think it was iSub) had better local-first / offline behavior than Apple Music or Spotify.

I think this would be pretty trivial to fix zed’s autoformatter settings.