What Will React Come Up With Next?  ## Metadata - Author: [[Changelog Master Feed]] - Full Title: What Will React Come Up With Next? - Category: #podcasts - URL: https://share.snipd.com/episode/f677fea8-5f3c-4dac-aba3-6fd948be61c6 ## Document Notes ## Highlights - **Next.js React Server Components Debate** - Next.js' integration of React Server Components via the use server directive is controversial. - Some see it as powerful, others as potentially sloppy and reminiscent of old PHP practices. Transcript: Speaker 1 The hubbub of the WebDev world right now is Next. JS is integration of React server components, specifically the use server directive, which lets you write React components that run SQL queries and presumably other server side Things. People's gut reaction to this has been all over the map. Maybe it sounds super powerful and expressive to you. Maybe it sounds super dangerous and sloppy. Me? It reminds me a lot of the index.php files we wrote at the turn of the century, which isn't something I want in my life anymore. But, I'm withholding judgement until I see more. In the wake of this divisive news came criticism and a claim for Next.js itself, even though it is the React team enabling and promoting the behavior, which leads us to our next headlines. Kent C. Dodds is a remix guy, so it's not a surprise that he prefers it over Next. But he gets asked a lot why he prefers it, so he wrote down his reasonings with the following disclaimer. Quote, I like to focus most of my time and attention on the positive side of software development. I would much rather write a post titled Why I Use Remix and written about the things I love about remix. I've already done this, but a lot of people have asked me specifically about Next.js and this post is for them. I'm not here to bash on Next.js. I'm just here to add an honest take of my personal perception and experience with Next.js. If you'd rather not hear negative things about Next, then I invite you to stop reading now, go outside and touch some grass. End quote. I'll give you the bullet points and you can click through for the full explanations if interested. Next.js doesn't always use or promote the web platform. Next.js is attached to Vercelle, both dev and easy deploy. Next.js is eating react. Next.js has too much magic. Next.js is getting overly complex. And next.js favors features over stability. ([Time 0:00:55](https://share.snipd.com/snip/9ab7b705-7c8d-4241-98b4-0d943519ecbc)) - **Lee Robinson Defends Next.js** - Lee Robinson defends Next.js as a framework that helps developers learn the web platform. - He affirms all Next.js features can work self-hosted and React Server Components are production ready. Transcript: Speaker 1 In response to Kent's post, Lee Robinson, who is the vice president of DX ever sell, makes the case for next.js with the following disclaimer. End quote. Kent is an incredible member of the React community. I've learned a lot from him over the years, especially his material on testing. And this blog actually uses a library he created, MDX Bundler. So thank you. If you're new here, I'm Lee. I work on Next.js. I've also made some courses about using Next.js before I joined Vercelle. Both Kent and I are passionate about the tools we use. I'm often asked about my opinions on Next versus other frameworks. Next post is for the folks in the Next.js community who are wondering about some of the points Kent brings up end quote. Once again, I'll give you his bullet points and you can click through for the full explainers if interested. Learning Next.js helps you learn the web platform. All Next.js features works self-hosted. Server components and server actions are independent of Vercelle. The React Canary channel is stable for frameworks like Next.js to adopt. And server components are production ready. ([Time 0:02:57](https://share.snipd.com/snip/00b486b8-fcb4-4658-88ae-a7f3afa9a6c0)) - **NixOS Progress on Reproducible Builds** - NixOS achieved reproducible builds of all packages and their ISO, improving trustworthiness. - Reproducible builds verify shipped binaries match their sources and haven’t been tampered with. Transcript: Speaker 1 The NixOS team has successfully performed a reproducible build of A, all packages that make it into the ISO and B, the building of the ISO itself. This is progress from their 2021 announcement which only had reproduced the individual packages. Why are reproducible builds important? Quote, while there are a number of side benefits, the main point of reproducible builds is that it gives us a reliable way to verify the binaries we ship are faithful to their sources And have not been tampered with anywhere in the build pipeline. ([Time 0:05:04](https://share.snipd.com/snip/f3292e91-6514-456b-a18e-7872fded88e8)) - **OpenSign as DocuSign Alternative** - OpenSign offers a free, open-source alternative to DocuSign for eSigning. - It features secure signing, audit trails, and API integration, with self-hosted or cloud options. Transcript: Speaker 1 But big progress. Exciting stuff. OpenSign is a project by OpenSign Labs with a mission to democratize the eSigning process, making it acceptable and straightforward for everyone. The easiest way to think about OpenSign is a free and open source alternative to DocuSign. The software currently features secure signing, a user-friendly interface, audit trails, and an API for integration into other software and services. Host it yourself as a React, Node, and MongoDB app or opt for their cloud hosted version. ([Time 0:05:54](https://share.snipd.com/snip/876053e0-7ccf-4018-87c8-a0d382eae193))