• Self-contained, concern-specific
building blocks
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
No content
Slide 14
Slide 14 text
Slide 15
Slide 15 text
Slide 16
Slide 16 text
Slide 17
Slide 17 text
Slide 18
Slide 18 text
• Self-contained, concern-specific
building blocks
• Allows a “divide and conquer”
approach where no particular part
needs be especially complex
Componentization
Slide 19
Slide 19 text
No content
Slide 20
Slide 20 text
No content
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
No content
Slide 23
Slide 23 text
• It’s plain javascript - It doesn't alter
the language semantics.
• XML is great for representing UIs in
element trees with attributes.
• It’s more concise and easier to
visualise the structure of your
application.
Slide 24
Slide 24 text
No content
Slide 25
Slide 25 text
• Templates encourage a poor
separation of concerns
• Display logic and markup are
inevitably tied together. They’re
highly cohesive.
• Keeping components small and
single-purposed lead to separation
of concerns
Slide 26
Slide 26 text
No content
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
~2004
Hybrid
~2010
Single Page Application
1994+
Server Driven
Slide 29
Slide 29 text
~2004
Hybrid
~2010
Single Page Application
1994+
Server Driven
Slide 30
Slide 30 text
~2004
Hybrid
~2010
Single Page Application
1994+
Server Driven
Slide 31
Slide 31 text
~2004
Hybrid
~2010
Single Page Application
1994+
Server Driven
Slide 32
Slide 32 text
~2004
Hybrid
~2010
Single Page Application
1994+
Server Driven
Slide 33
Slide 33 text
No content
Slide 34
Slide 34 text
No content
Slide 35
Slide 35 text
No content
Slide 36
Slide 36 text
No content
Slide 37
Slide 37 text
No content
Slide 38
Slide 38 text
No content
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
• Every time state is updated, it is
guaranteed to be up-to-date.
• No magical data binding.
• No model dirty checking
• No more explicit DOM operations –
everything is declarative.
Just Render the State. Every Time.
Slide 41
Slide 41 text
No content
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
In-Memory lightweight representation of the DOM
In-Memory lightweight representation of the DOM
On Every Update:
• React builds a new virtual dom
subtree
• Diffs the new tree with the old one
• Computes the minimal set of DOM
operations
• Batch executes all updates