Using Reason in traditional Enterprises
summary
Claims that Reason yields fewer runtime errors thanks to a strict type system, reports a four-person team building a progressive web app for a large European financial client, and shows the app running on Kubernetes with offline-first, mobile-first behavior plus WebSocket/SSE/polling. Work succeeds functionally but uncovers tooling and ecosystem gaps: multiple Reason/BuckleScript APIs, fragile third-party bindings, inconsistent stack traces, formatter/parens irritations and mismatched compiler versions breaking builds. Overall developer ergonomics impress while maturity and library support lag.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:14Why Does It Make Sense To Bring Emerging Technologies To Let's Say More Traditional Enterprises
- 5:05Api Stability
- 6:27Type System
- 7:07Pragmatic Paradigms
- 7:34Interrupts
- 9:37The Challenges That We Encountered
- 10:00Which Api To Use
related talks
29mAMA with Jared Forsyth
47mHow things are, and how they could be
33mReasonML and You - A Fireside Chat with Mike
17mDeveloper Experience Q&A
34mHow to build front-end web apps that scale
31mLessons learned from refactors and rearchitectures
44mLies we tell ourselves about developer infrastructure
49mScalable Best Practices for Your Development Team