Server Components Give You Optionality
not a prescription| Daniel Saewitz
I spend a lot of time reading (and participating in) discussions in the React community, across many different sites. Over the last few years I've seen an increasing amount of frustration and concerns from the community, questions about the motivations and intent behind React's development, and a growing disconnect between how the React team wants React to be used, and how the ecosystem is using React in practice. I've put together this talk to explain and clarify what I'm seeing argued about...| Mark's Dev Blog
Details on how React rendering behaves, and how use of Context and React-Redux affect rendering| Mark's Dev Blog
The official Essentials tutorial for Redux: learn how to use Redux, the right way| redux.js.org
My talk for React Summit US 2024 was on "Maintaining a Library and a Community". The main thesis is that maintainers do a lot more than just write features and fix bugs, and that really most of what we do involves thinking about and interacting with the users of our library. That includes answering support questions, writing docs, thinking about how versioning and backwards compatibility will impact people, and a lot more. Hopefully this proves useful to other maintainers, and peels back the ...| Mark's Dev Blog
The library for web and native user interfaces| react.dev
A dive into how we built Replay's React DevTools integration with our time traveling backend API| Mark's Dev Blog
A shorter look at how React rendering actually works| Mark's Dev Blog
Next.js 13.4 moves App Router to stable, Turbopack to beta, and introduces experimental support for Server Actions.| nextjs.org
Next.js 13 introduces layouts, React Server Components, and streaming in the app directory, as well as Turbopack, an improved image component, and the brand new font component.| nextjs.org
