Server side rendering React natively with Reason
summary
Claim is that React can be server rendered natively by compiling Reason components so one codebase runs on browser and server, implemented as serverReasonReact with renderToString renderToStream and renderToMarkup APIs compiled to JS and native. Benchmarks show large speed gains versus Node/Bun; production use covers parts of adrs (dashboard and workon) in a codebase with 5000 components, 20 front devs and 10 SPAs. Workable but beta, avoids component duplication and enables multicore and effect-driven patterns.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:01What is ReasonML
- 8:19ReasonML vs TypeScript
- 16:28React SSR challenges
- 23:36Reimplementing React server rendering
- 27:45Performance benchmarks
- 31:14Multicore and future
- 33:22Project status
related talks
44mServer Side Rendering from the trenches
35mGet started with Reason
38mBuilding Isomorphic Web Applications with React
41mReasonML: React as a Language and what the Future looks like
40mServer-Side Rendering 2.0? React Server Components
43mReact Applications on the Server
28mCross-Platform React
33mServer Components are React's superweapon in the Stack Wars
