Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
The framework that we wanted that day
Search
kkeeth
September 22, 2018
Technology
0
66
The framework that we wanted that day
kkeeth
September 22, 2018
Tweet
Share
More Decks by kkeeth
See All by kkeeth
とある EM の初めての育休からの学び
clown0082
1
1.5k
The history of Javascript frameworks: changes in front-end design philosophy
clown0082
2
140
Visually experience the beauty of mathematics with p5.js
clown0082
1
2.9k
Rediscover the joy of coding with Creative Coding
clown0082
0
1.5k
全員が意思決定する会社で開発者体験や生産性を見る大変さについて
clown0082
0
580
JavaScript × Mathematics go to Digital Art
clown0082
1
350
In-house study group at YUMEMI
clown0082
0
180
Playing Ionic Logo by p5.js
clown0082
0
240
Skills that employers recommend students to acquire
clown0082
1
280
Other Decks in Technology
See All in Technology
AWSを活用したIoTにおけるセキュリティ対策のご紹介
kwskyk
0
350
Ruby on Railsで持続可能な開発を行うために取り組んでいること
am1157154
3
140
ExaDB-XSで利用されているExadata Exascaleについて
oracle4engineer
PRO
3
240
Exadata Database Service on Cloud@Customer セキュリティ、ネットワーク、および管理について
oracle4engineer
PRO
2
1.5k
急成長する企業で作った、エンジニアが輝ける制度/ 20250227 Rinto Ikenoue
shift_evolve
0
130
大規模アジャイルフレームワークから学ぶエンジニアマネジメントの本質
staka121
PRO
3
1.1k
依存パッケージの更新はコツコツが勝つコツ! / phpcon_nagoya2025
blue_goheimochi
3
210
RemoveだらけのPHPUnit 12に備えよう
cocoeyes02
0
280
組織におけるCCoEの役割とAWS活用事例
nrinetcom
PRO
4
130
EMConf JP 2025 懇親会LT / EMConf JP 2025 social gathering
sugamasao
2
190
30→150人のエンジニア組織拡大に伴うアジャイル文化を醸成する役割と取り組みの変化
nagata03
0
150
クラウド関連のインシデントケースを収集して見えてきたもの
lhazy
5
420
Featured
See All Featured
YesSQL, Process and Tooling at Scale
rocio
172
14k
The Straight Up "How To Draw Better" Workshop
denniskardys
232
140k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
40
2k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
32
2.1k
How to train your dragon (web standard)
notwaldorf
91
5.9k
For a Future-Friendly Web
brad_frost
176
9.6k
Visualization
eitanlees
146
15k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
100
18k
Designing for Performance
lara
604
68k
Making Projects Easy
brettharned
116
6k
A Philosophy of Restraint
colly
203
16k
How to Think Like a Performance Engineer
csswizardry
22
1.4k
Transcript
The framework that we wanted that day ... k-kuwahara @kuwahara_jsri
@clown0082 Sep 22, 2018 ʲୈ4ճʳJSϑϨʔϜϫʔΫ(·ͨϥΠϒϥϦ)× ϏΞόογϡ ॳ৺ऀษڧձ
About me const my_info = { Workplace: ‘Yumemi Inc’, Community:
‘Riot.js, Ionic, Dist’, Favorites: ‘CLI made by Node.js’, PokemonGO: ‘TL38’ }
github.com/riot
Sorry... " As usual, there is no line of source
code. Plz feedback for me called “Masakari” about my English
Conclusion
Please use whatever you like
The appearance of the first framework
so-called “Chaos” Pure JS with
so-called “Chaos” Pure JS with
The load named frameworks for JavaScripts
The former three major frameworks
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
React and Componentry
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!
ɹ Header Footer Navigation Bars Main Contents2 Main Contents3 Main
Contents1 Hero Menu Componentry
Flux image by: https://www.npmjs.com/package/flux
Componentry One-way data binding State management Idea of so-called Flux
Things for View to the end Features
BTW, start to reduce the weight of the library
Attack to Vue.js
None
We use two-way data bindings! ※That's not all Vue.js is
componentry, also uses flux-based state management
GitHub stars
GitHub stars
GitHub stars
Conclusion (again)
Please use whatever you like
Have a nice JavaScript life!!
Publicity
We’re looking for Engineers!!
None
None