tRPC v11, Netlify vs. Next.js, and Firefox Gets PWAs (Kind Of)

Key takeaways

tRPC v11 introduces significant improvements for building typesafe APIs, streamlining the development process.
Netlify raises concerns over Next.js's lack of adequate support for hosting applications outside of Vercel.
Firefox's addition of PWA support may not meet developer expectations for a fully native app experience.
The landscape of CSS-in-JS frameworks is changing, with styled-components moving into maintenance mode.
Personal segments bring a lighter note to the podcast, showcasing hosts' interests in literature and gaming.

Summary

tRPC v11 Release

The team behind tRPC has officially declared version 11 production-ready. This exciting update allows developers to create typesafe APIs with shared types between client and server, reducing boilerplate code. The new version includes integration with TanStack Query v5, the ability to send and receive non-JSON data content types, improved support for React Server Components (RSCs), and the capability to stream responses, making it a robust upgrade for developers.

Netlify vs. Next.js Debate

The podcast discusses an open letter released by Netlify regarding the difficulties posed by Next.js applications not hosted on Vercel. Netlify’s concerns include the lack of adapter support, poorly documented serverless deployment documentation, and Next.js’s failure to adhere to open web standards. They highlight significant challenges and recommend better communication and documentation to enhance the experience for hosting providers.

Firefox's PWA Update

Firefox is set to add support for Progressive Web Apps (PWAs), although the team isn't overly enthusiastic about the extent of the support. They noted that the PWA experience in Firefox will maintain a browser-like feel rather than resembling native app behavior, which may not fully meet developer expectations.

Additional News Highlights

The discussion touches on various other important updates, including styled-components entering maintenance mode, signaling a shift in the CSS-in-JS landscape towards broader frameworks like Tailwind. Furthermore, they introduce a new JavaScript runtime called Bare, and highlight a partnership between Windsor and Netlify that aims to streamline deployment processes directly from developers' IDEs.

What's Making Us Happy

In the segment that explores personal joys, each host shares something uplifting. Paige discusses the novel 'Squeeze Me' by Carl Hiaasen, highlighting its humorous take on Florida's quirks. TJ expresses excitement about the upcoming release of Mario Kart World on the Nintendo Switch, featuring new gameplay elements, while Jack appreciates his journey with the guitar through the Pickup Music platform.

Show notes

The tRPC team declares v11 officially production-ready. tRPC allows devs to build typesafe APIs with types that can be shared on the client and server, and now it has support for TanStack Query v5, the ability to send and receive non-JSON data content types, improved support for RSCs, and the ability to stream responses.

After the Next.js security incident a few weeks back, Netlify writes an open letter around the challenges Next.js poses when not hosted on Vercel. It raises valid points like a lack of adapters, no production grade documentation for serverless deployments, no visible roadmap or release schedule, and a disregard for open web standards, among others.

Firefox is finally adding support for progressive web apps (PWAs), but its web app support will intentionally not look, feel, or behave the same way similar features do in other browsers.

News:

Paige - tRPC v11
Jack - Firefox will support PWAs (finally)
TJ - Next.js Netlify deployment drama

Bonus News:

What Makes Us Happy this Week:

Thanks as always to our sponsor, the Blue Collar Coder channel on YouTube. You can join us in our Discord channel, explore our website and reach us via email, or talk to us on X, Bluesky, or YouTube.