Phoenix Framework

“it's hard to argue with a 10x reduction in memory usage and latency”

“It has brought me joy for almost 9 years now and I wouldn't trade it for the world!”

“This is one of numerous things Elixir and Phoenix get right with the database layer”

“I'm really excited about the concurrency and distributed nature of Erlang”

“It's token efficient (because of code generator), has great static analysis, and terse (because functional).”

“Just so quick and easy, and the LLM seems to get things right quite often.”

“IMO Phoenix[0] is what Wayland should have been: a reimplementation of X11.”

“If you downgrade to Phoenix 1.6 and learn from there, you should be fine.”

“the differences in Phoenix 1.7 are enough to break the tutorials enough to confuse a newbie”

“It's the only Elixir package where I've encountered substantial friction during upgrades.”

“which many Elixir libraries (such as Phoenix and Ecto) uses to great effect”

“Phoenix especially uses a lot of compile-time macros and it can be a steep learning curve”

“I didn't understand how a Phoenix app booted, didn't know where to edit my config.”

“It really takes surprisingly little volume to cripple a return-hello-world Phoenix app that indirects the "hello world" behind way too much middleware and message passing”

“Phoenix often has kid-appropriate documentaries, and sometimes ARD and ZDF. Phoenix is the channel they watch the most, by far.”

“LLMs seem to have an easy time with Elixir and Phoenix in my testing.”

“With Phoenix you can write actually 0 code that runs on the client, just the backend and html templating.”

“delightfully fast and not having to deal with two entirely different application stacks”

“I get a similar feeling from Elixir and Phoenix without the method_missing foot gun.”

“ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO”

“Elixi/Phoenix is more exlicit in that regard, making long-term support (as in anything past first week) a breeze.”

“I already knew Phoenix well, LiveView fits my use case, and websockets setup with Phoenix is very clear”

“Phoenix supervision trees ended up being especially useful for isolating failures between model calls”

“I’ve moved all of my personal sites over to it and it’s been running for almost a year now.”

“there are other technologies that solve for that at a more fundamental level (htmx, phoenix)”

“Phoenix to me basically "fixed" all the things I didn't like about Rails”

“The Phoenix framework applies this concept to the web, and it works very well”

“Phoenix is a great web framework, and I think all of it is quite approachable.”

“It also helps that the app itself is on the Elixir BEAM (Phoenix) so everything "just works" across all machines.”

“Elixir with Phoenix and Liveview is super bloated”

“with elixir/phoenix you just push all that complexity to the backend and trust in websockets and the BEAM”

“Manageable scale, hides details well until you need to tweak them, sensible defaults for CSS and JS interactions.”

“we were measuring responses in microseconds on local dev machines, and under 5 ms in production with zero optimization”

“I expect Phoenix to be the more technically interesting project, since it's deliberately breaking from the X11 spec.”

“It's extremely nice! Coming from the React and Next.js world there is very little that I miss.”

“I just use phoenix with some special hotkeys to move windows into positions and tile them.”

“they are not wasting resources making slick start-upy marketing fluff”

“reusing an old conn value and/or not using the latest conn value in Plug/Phoenix”

“I also switched to Phoenix using Js only when absolutely necessary.”

“While the Phoenix documentation is stellar, I found it difficult to find good resources on best practices.”