What's Next for Phoenix
summary
Phoenix just shipped 1.0 and the near roadmap names three concrete things: Channel presence that tracks who joins and leaves across crashed nodes and Heroku dynos (hard distributed edge cases, aim for end‑of‑year), gex internationalization integration to emit gettext files at compile time, and multiplatform Channel clients (JS Swift Objective C Java) already running. Longer term experiments build a GraphQL server style approach for collocated declarative queries, automatic caching and parallelized data fetching for server‑rendered views.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:04Phoenix in Production
- 1:56Phoenix beyond the browser
- 7:46Inside View
- 16:48Implicit View Data Requirements
- 19:41Controller Mayhem
- 30:27GraphQL is naturally parallelizable
related talks
54mPhoenix 1.2 and Beyond
01h 00mPhoenix a Web Framework for the New Web
40mTaking Off with Phoenix
45mPhoenix a web framework for the new web
32mWhy I choose Phoenix
44mRise of The Phoenix - Building an Elixir Web Framework
01h 00mPhoenix: an Intro to Elixir's Web Framework
50mPhoenix Framework: a (Truly) Fullstack Stack for Building Real-Time Web
