kofno
Trending in Discussions
The obligatory hello world thread!
Who are you and where are you from? :stuck_out_tongue:
New
Hey there,
It’s been more than a year since we started using LiveView as our main UI library and building a whole library of UI componen...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
In my third year of college, around 2010, I found Erlang. A few years later, I found Elixir. I liked the ideas at once: many small proces...
New
I’ve been tinkering with Lynx (by José) via hold_ledger. I used AI to write the code, a separate specification, the tests, and the Lean p...
New
A remark @Garrison made…
..has already inspired a thread for the technical side of reclaiming our internet, but there is of course anot...
New
Hi everyone! I’m the developer of PaperForge, and I’ve been working on something alongside it that I’d like your opinion on.
I’m conside...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #security
- #elixirconf-eu
- #processes
- #api
- #forms
- #hex










Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Mandemus
I’m new to Phoenix but It is certainly the killer feature to me.
I’m pretty sure most people are interested in Phoenix for it’s real-time possibilities and not merely as a REST framework. The effort they are putting into channel presence features is good evidence of that.
kofno
Channels is why I’m considering Phoenix. But I’m just not sure I want to rely on that connection for sustaining a session. I still need a token, whether it’s JWT or just a user id in a secure cookie.
ckhrysze
Even without channels, I’d be interested in Phoenix for the performance over Rails. With channels, it seems likely there is little I’d want to do with a webapp that it can’t do, and do well. Regarding auth, even will channels, I’m seeing a lot of mobile app based tooling that prefers JWT anyway, so I don’t think that and channels are mutually exclusive.
AstonJ
I think many people feel this way
There were some recent criticisms that Elixir (and Phoenix) were not different enough - but I think the critics failed to appreciate the draw of familiarity. If people wanted something radically different to Rails then they have plenty of Ruby options (Lotus, Volt, Trailblazer etc). But that’s not what most Rails devs want - they want top of the class performance.. and Phoenix gives that - while at the same time - moving towards better paradigms, practises etc.
At least that’s how I see it
ckhrysze
Its hard for me to believe people think Elixir isn’t different enough to matter, I think all of 2 days with it convinced me I needed to unlearn several things, and once I did, that it was a new, wonderful and different language.
I can see that argument applied to phoenix, but I also think its a good thing. The surface similarities run a bit deeper, though I think just because its also basically following the MVC pattern. But as Chris McCord has said, you don’t end up with a phoenix app, you end up with an app that happens to use phoenix, and I believe that matters.
kofno
A strong appeal of Phoenix for me is the familiarity. There are enough Rails touch points that I don’t feel overwhelmed. It also helps that many of the differences in Phoenix address areas of Rails that I perceived as weaknesses.
NobbZ
Currently I don’t use channels in my small personal and still private project, but as soon as the back-end is ready, there is planned to use heavy channelsthrough front-end