Phoenix 1.6 is organizing around WebSockets with Phoenix LiveView and presents a paradigm shift in web frameworks.
Phoenix 1.6 Release Candidate is out and I am currently in the process of assessing a migration to that version from the legacy codebase started on Phoenix 1.3 running Folkbot.com today.
The current folkbot.com codebase has been an ongoing hobby project since Phoenix 1.3. and contains many experiments and implementation patterns. Implementations derived from the first Phoenix book, alchemist.camp, elixircasts, changelog.com and so on. Some of the original implementations came from blog posts before the official book which established unofficial community-style guidelines.
Phoenix 1.6 is reorganizing around WebSockets and is less about HTTP and REST (although these obviously are massive pillars of the ecosystem). WebSockets present a paradigm shift in the internet and web. Phoenix LiveView brings WSS into the center and Phoenix LiveView is maturing as the keystone of the Elixir Phoenix ecosystem.
It is extremely difficult to overstate the importance of WebSockets manifested in Phoenix LiveView.
On Folkbot.com the technical debt has gotten to a position where I am seriously considering terminating the development of the current codebase and cherry-picking custom code and implementations and moving them over to a clean and minimal implementation using Phoenix 1.6.
This is my current plan
Accounts and Users https://www.folkbot.com/posts/24-phoenix-1-6-accounts-users
Snowflake ID for Users https://www.folkbot.com/posts/25-snowflake-id-for-users