Framework · 2014–now · Cloud Scale
Phoenix / LiveView
Real-time Elixir on the BEAM with HTML-over-the-wire before it was cool. Small but fiercely loyal community.
Phoenix stuck where teams already bet on Elixir because channels and LiveView ship features faster than SPA ceremonies. It failed to displace Rails or Django because language adoption is the bottleneck, not framework quality. The admiration is real; the job listings are not.
Context
Split everything, then pay for the glue
Hyperscale patterns escaped the companies that needed them. Containers unified packaging; Kubernetes became the cloud OS; microservices and NoSQL were sold as defaults. Mobile-first stuck because screens changed. Cargo-cult distributed systems stuck around as invoices. The durable move was packaging and ops maturity — not rewriting every app into a mesh.
Compare with
Related
Language · 2011–now
Elixir
BEAM reliability with modern syntax. Phoenix and LiveView keep the torch for pragmatic functional web.
Language · 1986–now
Erlang / OTP
Let it crash, supervision trees, and nine-nines uptime. The telecom substrate that outlived every "modern" backend pitch.
Framework · 2020–now
Hypermedia / htmx
HTML as the engine of application state — a deliberate counter to SPA maximalism.