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
Maintainable React UIs using Cosmos.js
Search
Ovidiu Cherecheș
April 28, 2015
Programming
3
250
Maintainable React UIs using Cosmos.js
Ovidiu Cherecheș
April 28, 2015
Tweet
Share
Other Decks in Programming
See All in Programming
GoのGenericsによるslice操作との付き合い方
syumai
3
720
20250628_非エンジニアがバイブコーディングしてみた
ponponmikankan
0
620
Quand Symfony, ApiPlatform, OpenAI et LangChain s'allient pour exploiter vos PDF : de la théorie à la production…
ahmedbhs123
0
120
コードの90%をAIが書く世界で何が待っているのか / What awaits us in a world where 90% of the code is written by AI
rkaga
50
32k
Discover Metal 4
rei315
2
110
What Spring Developers Should Know About Jakarta EE
ivargrimstad
0
380
PHP 8.4の新機能「プロパティフック」から学ぶオブジェクト指向設計とリスコフの置換原則
kentaroutakeda
2
710
『自分のデータだけ見せたい!』を叶える──Laravel × Casbin で複雑権限をスッキリ解きほぐす 25 分
akitotsukahara
1
600
エラーって何種類あるの?
kajitack
5
340
Modern Angular with Signals and Signal Store:New Rules for Your Architecture @enterJS Advanced Angular Day 2025
manfredsteyer
PRO
0
170
技術同人誌をMCP Serverにしてみた
74th
1
530
ruby.wasmで多人数リアルタイム通信ゲームを作ろう
lnit
2
330
Featured
See All Featured
GraphQLの誤解/rethinking-graphql
sonatard
71
11k
Optimizing for Happiness
mojombo
379
70k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
How to Think Like a Performance Engineer
csswizardry
24
1.7k
A better future with KSS
kneath
239
17k
The Power of CSS Pseudo Elements
geoffreycrofte
77
5.8k
Scaling GitHub
holman
459
140k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
331
22k
Producing Creativity
orderedlist
PRO
346
40k
Designing for Performance
lara
609
69k
Building Adaptive Systems
keathley
43
2.6k
Fireside Chat
paigeccino
37
3.5k
Transcript
Hello.
Why do UI devs change frameworks so often?
Why do UI devs change frameworks so often? A. Because
we constantly want to learn new stuff B. Because web browsers have evolved a lot in the last years or...
C. Because a change in the old framework feels like
this:
So you found a new framework... "This time it's going
to be different."
Things are going great... • Trying & learning new stuff
every day • No technical debt and haunting hacks • No need to refactor with every feature
This (framework) might be the one.
2 years later...
Why do we have so many bugs?
Why is writing code so hard to debug?
Don't be naive. React is not your soulmate.
What makes a codebase go bad in time?
None
None
How to understand an implicit codebase: 1. Grep the entire
project for that entity 2. Grep the entire project for the file name 3. Ask a friend, or... 4. ...read the entire source code.
You have to understand the entire project to figure out
something in a module. This is not scalable.
A maintainable codebase is explicit and intuitive.
How do you write explicit code? • Dependencies should be
expressed inside- out • Every module should expose a standalone, testable API • Every UI component should be an entry point.
Maintainable React UIs using Cosmos.js Bear with me...
ComponentTree Serialize and reproduce the state of an entire tree
of React components.
ComponentPlayground Minimal frame for loading and testing React components in
isolation.
Demo.
Thank you! // Ovidiu Cherecheș // Leading the Analytics UI
at Hootsuite //
[email protected]
// twitter.com/skidding // github.com/skidding