Domain Modeling and Application Architecture in ReScript
summary
ReScript's recent improvements (async/await, JSX/React refactor, new standard library) are presented alongside an argument for using ReScript's type system for domain modeling instead of TypeScript. The talk shows concrete examples where ReScript types provide stronger safety than TypeScript and examines application architecture patterns, with practical demos for data parsing and error handling.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 3:15What is ReScript
- 7:10Impossible states with types
- 15:22Dragon model with algebraic types
- 23:47Business processes and errors
- 28:52External data and parsing
- 37:26App architecture sandwich
- 40:19Onion architecture
- 47:13Summary and Q&A
related talks
59mWhy I Moved Away from TypeScript in My React Projects and Where I Went
44mWhy I Stepped Away from React in My TypeScript Projects and Where I Went
21mHow Typescript Can Power Design Systems
27mLightning Talks - Day 1
12mTalkScript: Ron MacCracken from Centric Software
33mTalkScript with the TypeScript Team
19mDaria Caraway at JSworld Conference about TypeScript
27mReasonML for Skeptics
