What’s not to love about Reason?
summary
ReasonReact adoption story with concrete tradeoffs: a team ports a project to ReasonReact and relies on BuckleScript interop for JS snippets, hitting surprises like a logging quirk where an array shows 71 objects vs 2 logged items because lists print nested and js console truncates deep nesting. External bindings use bsset/bsget syntax and dead‑code elimination can hide wrappers. Cognitive load matters: working memory is limited (about seven ± two items) and fragmented docs (Reason, BuckleScript, OCaml, React) raise extraneous load while NPM growth numbers (≈5M users, ≈1M new in six months) pressure better learning paths.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:22Terminology
- 7:44Logging Debugging
- 15:22Cognitive load theory
- 16:40Schema
- 20:12I found it easy
- 21:24The learners pathway
- 23:17Conclusion
