The framework that we wanted that day

1. The framework that we wanted that day ... k-kuwahara @kuwahara_jsri @clown0082 Sep 22, 2018 ʲୈ4ճʳJSϑϨʔϜϫʔΫ(·ͨ͸ϥΠϒϥϦ)× ϏΞόογϡ ॳ৺ऀษڧձ
2. About me const my_info = { Workplace: ‘Yumemi Inc’, Community: ‘Riot.js, Ionic, Dist’, Favorites: ‘CLI made by Node.js’, PokemonGO: ‘TL38’ }
3. github.com/riot
4. Sorry... " As usual, there is no line of source code. Plz feedback for me called “Masakari” about my English
5. Conclusion
6. Please use whatever you like
7. The appearance of the first framework
8. so-called “Chaos” Pure JS with
9. so-called “Chaos” Pure JS with
10. The load named frameworks for JavaScripts
11. The former three major frameworks
12. 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
13. React and Componentry
14. 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!
15. ɹ Header Footer Navigation Bars Main Contents2 Main Contents3 Main Contents1 Hero Menu Componentry
16. Flux image by: https://www.npmjs.com/package/flux
17. Componentry One-way data binding State management Idea of so-called Flux Things for View to the end Features
18. BTW, start to reduce the weight of the library
19. Attack to Vue.js
21. We use two-way data bindings! ※That's not all Vue.js is componentry, also uses flux-based state management
22. GitHub stars
23. GitHub stars
24. GitHub stars
25. Conclusion (again)
26. Please use whatever you like
27. Have a nice JavaScript life!!
28. Publicity
29. We’re looking for Engineers!!