Mastodon

I can’t tell which is louder, the fans on this 2019 Intel MacBook Pro running what my therapist calls a dangerous number of tabs in a single Chrome window or React fans on Twitter reading a light but fair criticism of Next.js release stability.

Next.js bundles a Canary version of React to support a feature that Next has marked as stable (app dir): https://nextjs.org/blog/next-13-4#nextjs-app-router

This follows React design goals: https://react.dev/blog/2023/05/03/react-canaries#tldr

However, the weak link here is that React doesn’t guarantee semver in Canary releases, so *of course* things are going to break. If any deps up the chain break semver, your release also breaks semver.

Fred is right to call this out: https://twitter.com/FredKSchott/status/1673342700651704330

Really appreciate all of the kind words in this thread—they really mean a lot.

I’ve learned an overwhelming amount running this project—and not just on the technical side.

I’ve learned things about our industry, funding, and investment that have really challenged my views on open source—I’m still trying my best to process things and prune off cynicism from the truth.

But regardless, y’all are amazing—I really appreciate every single one of you. Couldn’t have done any of this without y’all ❤️

The Reddit API pricing changes and subsequent tire-fire executive response is further evidence that we must take great care to look at how communities (and products!) are funded before we sink our time, hard work, and attention into them.

two days of amazing talks and chats with attendees followed by one or more days of replaying all of those conversations to file any personally embarrassing moments in long term memory

conferences! 😅🫠

I’m pretty level-headed most of the time but I turn 100% feral Karen when—in the year of our New Zealand singer-songwriter Lorde 2023—the volume buttons on my keyboard are STILL rendered useless attempting to control an HDMI or USB-C output.

I continue to be surprised that new platform-level CSS features seem to be rolling out so fast that framework and library abstractions on top of CSS are having a hard time keeping up.

Feels unprecedented but it’s a huge vote in favor of Writing CSS as CSS in CSS.

1. 👏 Hire someone that’s good at HTML and CSS to build components independent of JS frameworks 👏
2. Plug components into a JS framework and layer on behavior later
3. Pay HTML/CSS devs what they deserve for giving part of your code-base longer shelf life than unpasteurized milk

10 years of web performance debate:

“Your site is only faster because it does less”
“Yep”
“It’s not fair to compare them”
“Why?”
“It does fewer things”
“Yeah—to make it faster”
“That’s not fair”
“Why?”
“I want mine to do more”
“Okay—but it will be slower”

I need to issue a correction for an earlier (deleted) toot about Next.js’ <Image> and WebP support.

The default `formats` value is `image/webp` https://nextjs.org/docs/pages/api-reference/components/image#formats

And using the Accept header to fallback to the original format: https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation/List_of_default_Accept_values#values_for_an_image

With that reading it suggests that a JPEG or PNG source would work fine on Safari (prior to Mac OS Big Sur)—though I doubt a newer format input would work there but that’s a much smaller problem.

Appreciate the pushback @flq!