Flight.js
summary
Flight is a tiny component layer that runs all of twitter.com and most of TweetDeck and has been battle‑tested for about a year. Each component maps to a single DOM node, manipulates that node, and communicates only by firing and listening to DOM events — leveraging event bubbling for decoupled communication. Data logic lives in separate components, and tests use flight‑jasmine to give a fresh instance per spec so components are easy to unit test and compose.
AI-written summary · about
chapters (11)
- 0:00Start
- 5:53Necessary complexity
- 6:05Adding features means adding to the mental overhead of understanding the app
- 7:39Flight aims to completely decouple our application components
- 8:17Components have a simple contract with the outside world
- 10:03Make greater use of the DOM
- 10:45Inherent hierarchy
- 15:04Toggle
- 15:40Atomic components make for great tests
- 20:54Flight doesn't prescribe a templating engine, where you keep state or how you structure data
- 22:22Bring your own architecture
related talks
23mYou should be using Twitter's Flight framework.
37mMeteor - A Full Stack Framework For Building Pure JavaScript Apps
25mBuilding the Next Generation of Airlines Websites
30mJavascript @ Uber
31mHeaven & Hell JavaScript ... everywhere?
58mFrontin' like a Back-er
07mLightning Talk: A Backend Engineer's Vue of Front-End Development
44mMicro Frontend: the microservice puzzle extended to frontend
