Functional Frontend. Practical survival guide for backend engineers.
summary
Claim: front end forces different concerns — human interaction, a wild JavaScript ecosystem, and brittle bindings. Practical notes list actual tools and outcomes: TypeScript is pervasive but easy to lie to, Scala.js bindings break so prefer scalably-typed or native Scala libraries; React is common while Diode beats Redux ergonomically; Sangria and new Caliban for GraphQL; prefer SSE over WebSockets for many cases; use npm or yarn plus webpack or sbt-web/scala-js-bundler for bundling.
AI-written summary · about
chapters (6)
- 0:00Start
- 22:44SOMETHING DIFFERENT? Udash Korolev Play
- 23:46redux diode react refetch
- 30:18HOW DOES IT WORK? • Servers exposes schema (types, operations) • Client codebase contains queries Code can be generated based on queries and schema
- 42:41GRAPHQL IS A THING
- 43:04NPM AND WEBPACK ARE INEVITABLE
related talks
49mFront Ends for Back End Developers
01h 10mThe Future of Frontend Panel
29mRethinking Frontend Development
22mHow to Master Frontend Development: Survival Guide by Lilit Tadevosyan (Arm) | JSConfAM19
49mSOLID Frontend Architecture. Do we need it? Yes!
45mDo Frontend Devs dream of Backend functions?
01h 22mAnti-fragile frontend development
21mFrontend-centered Development: the Future of Web Development