Dumb question: does Phoenix have out-of-the-box support of a development model where you can create a stateless web app?
I ask because I feels like Phoenix is rallying around the stateful approach of LiveView and just want to ensure that model isn't the only model of development Phoenix will support (short and long term).
Yes it does. By default, any Phoenix application works this way just as any other app.
One of the biggest perks to the BEAM VM is how well it handles managing state though.
Most other languages aren't designed to do this well, so stateless web apps focus on just passing information from the client to somewhere else that holds the state (database, redis, etc).
Nothing is really stateless, it's just a question of where you decide to hold the state.
I ask because I feels like Phoenix is rallying around the stateful approach of LiveView and just want to ensure that model isn't the only model of development Phoenix will support (short and long term).