The framework that
we wanted that day ...
k-kuwahara @kuwahara_jsri @clown0082
Sep 22, 2018 ʲୈ4ճʳJSϑϨʔϜϫʔΫ(·ͨϥΠϒϥϦ)× ϏΞόογϡ ॳ৺ऀษڧձ
Slide 2
Slide 2 text
About me
const my_info = {
Workplace: ‘Yumemi Inc’,
Community: ‘Riot.js, Ionic, Dist’,
Favorites: ‘CLI made by Node.js’,
PokemonGO: ‘TL38’
}
Slide 3
Slide 3 text
github.com/riot
Slide 4
Slide 4 text
Sorry... "
As usual, there is no line of source
code.
Plz feedback for me called
“Masakari” about my English
Slide 5
Slide 5 text
Conclusion
Slide 6
Slide 6 text
Please use whatever
you like
Slide 7
Slide 7 text
The appearance of
the first framework
Slide 8
Slide 8 text
so-called “Chaos”
Pure JS with
Slide 9
Slide 9 text
so-called “Chaos”
Pure JS with
Slide 10
Slide 10 text
The load named frameworks
for JavaScripts
Slide 11
Slide 11 text
The former three major frameworks
Slide 12
Slide 12 text
Thought of expanding HTML to create dynamic web apps
Two-way data bindings
Modularization of JavaScript source code
Thought of MVVM
Flexible expression and extensibility
Features
Slide 13
Slide 13 text
React and Componentry
Slide 14
Slide 14 text
It is not two-way data binding!
Unify the flow of data
and manage the state!
※That's not all
Extension of HTML is painful.
Let's go with components!
Slide 15
Slide 15 text
ɹ
Header
Footer
Navigation Bars
Main Contents2 Main Contents3
Main Contents1
Hero Menu
Componentry
Slide 16
Slide 16 text
Flux
image by: https://www.npmjs.com/package/flux
Slide 17
Slide 17 text
Componentry
One-way data binding
State management
Idea of so-called Flux
Things for View to the end
Features
Slide 18
Slide 18 text
BTW, start to reduce
the weight
of the library
Slide 19
Slide 19 text
Attack to Vue.js
Slide 20
Slide 20 text
No content
Slide 21
Slide 21 text
We use two-way data bindings!
※That's not all
Vue.js is componentry,
also uses flux-based
state management