Sorry not sure what the claim is here, but we’ve worked very, very diligently to retain backwards compatibility for the last 10 years. There’s a reason we are 1.8 and not Phoenix v6 like you see most other places. In every release we have step by step guides to bring your existing apps, optionally, up to speed. But in any case I’m going to take your negative and flip it:

You could almost certainly in half effort langauge tell phoenix.new “check out this upgrade guide/phoenixdiff page and bring my app up to speed” and it would just do the thing and make sure your app builds/tests pass so in that regard this is a win for your project structure evolution criticisms ¯_(ツ)_/¯

demo:
https://x.com/chris_mccord/status/1923417060593356889

Blog and open registration coming next week, and some fun details in my ElixirConfEU keynote when it gets published.

This looks amazing. @chrismccord I’m curious if it is using Tidewave? Will we be able to plug in an LLM of choice? And even though the rate of change will make this answer obsolete, is there an LLM you’ve noticed currently performs better at agentic coding for this stack?