~/talk

Create Architecture and not Frameworks

Talkat JavaScript fwdays'17 · on Saturday, 2017-04-22· [frontend-architecture]
slides:none on file

A concrete recipe: a small manifest lists JS and CSS files, the host app lazy-appends them to head and uses a react-module-container to instantiate by a global ID from a module registry, then calls angular.bootstrap (or equivalent) to mount the legacy app into a React DOM node. Lifecycle hooks forward updates (call Angular digest) and teardown destroys scopes. Result: independent, lazily loaded modules, legacy Angular or React left unchanged, independently deployable and updated by swapping manifests rather than rebuilding the host.

AI-written summary · about

  1. 0:00Introduction
  2. 1:51Legacy frameworks and iframes
  3. 6:10Ideal architecture for large apps
  4. 13:50Demo: Angular in React
  5. 21:35react-module-container library
  6. 28:43Isolated lazy-loaded modules
  7. 30:51Library code deep dive
  8. 34:09Where this architecture helps
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.