This browser caching change kills the utility of cross-site resource CDNs like Google Fonts.

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

Self-hosting fonts can improve performance compared to using Google Fonts due to cache partitioning in browsers.

Time to Say Goodbye to Google Fonts: Cache Performance

Invalidating the old performance argument

That’s why I appreciate Next.js adding automatic self-hosting for Google fonts, a really nice QoL feature.

As I understand, the change is due to the HTTP cache partitioning which affects not only Google Fonts but every online resource loaded by HTTP (libraries, images, resources).
This means that we should move from third-party CDN resources to host all our resources in the same domain origin.
Does that mean that also API requests shouldn’t happen in the client but now in the server in case of build our own caching solution?
Let me know if I didn’t get something.