Tech Regrets at Spectrum

on YouTube ↗17m

" summary

Three-person team builds Spectrum for two years, then GitHub acquires it, and the concrete regrets shape future choices: not using react-native-web forces full mobile rewrites; rolling own server-side rendering instead of Next.js causes months of brittle infra work; choosing RethinkDB changefeeds hits scaling limits (clusters fail and individual changefeeds collapse beyond ~50–100 listeners) and causes repeated outages; shipping a Draft.js WYSIWYG wastes months—reverting to plain markdown proves simpler and far more reliable.

AI-written summary · about

" chapters (11)

1. 0:00Intro
2. 0:30Show of hands
3. 1:25Background
4. 2:35React Native Web
5. 5:25Experiment
6. 6:10Serverside rendering
7. 8:55Rethink DB
8. 11:55Choosing your technologies
9. 12:45Community size and active maintenance
10. 13:35Draft checkers and WYSIWYG editing
11. 16:05Lessons learned

" related talks

• 43mPanel DiscussionKrzysztof Magiera, Nicola Corti, Lorenzo Sciandra, Charlie Cheever, Monica Restrepo, Marcin Skotniczny, Jessica Lo · App.js Conf 2022
• 01h 06mPanel DiscussionChristopher Chedeau, Lee Byron, Sophie Alpert, Dan Abramov · React London 2017
• 40mHow I learned to love ReactDavid Mark Clements · Codemotion Rome 2016
• 43mRethinking SPAs: web-native appsDavid Leitner · Agent Conf 2020
• 21mFrontend-centered Development: the Future of Web DevelopmentDerrick Reimer · backendlessConf_ 2019
• 20mLarge Scale Projects Challenges (NextJS - Contentful)Leonidas Mamais · React Summit 2022
• 23mTeam × TechnologyJames Ide · React.js Conf 2016
• 29mLessons from Using Bleeding Edge Tech in a StartupViktor Eriksson · ReactiveConf 2018