Butterfly Effect: the Story about One Technical Decision
summary
Wrike switches the frontend to Dart and accumulates 1.5 million lines of Dart while R&D grows almost tenfold the claim is that Dart’s strong sound type system with runtime checks catches class and type errors earlier the toolchain delivers aggressive tree shaking and deferred loading so the client ends up around 20 MB gzipped bundle what actually breaks are ecosystem and framework support especially AngularDart and some third party libraries so recruitment and community maintenance become the real cost and the choice proves to be a tradeoff not a silver bullet
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:18My first technical decision
- 1:42The problem
- 3:42The Butterfly Effect
- 5:58JavaScript
- 7:45Maslow Pyramid
- 9:34Type System
- 11:57Structural Type System
- 13:22Ecosystem
- 15:51Typescript
- 16:23Scalability
- 16:46Dead Code Elimination
- 17:02Tree Shaking
- 18:19Different Loading
- 18:53Support
- 21:11Recruitment
- 21:30Dart Developers
- 23:54Restaurant Paradox
related talks
31mFlutter with 50+ Engineers
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
38mDart: a language optimized for the front end
45mBuilding Products Full-Stack with Dart and Flutter
31mTaming the Beast: Managing a really ambitious codebase
54mTipping the Scale
22mArchitecture First: Foundations for Long Term Success
30mFlutter at scale-experience from 25+ Flutter Devs working together on a mobile banking app