Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by Alifatisk on Friday October 17, 2025 @05:56AM (#45614900)

> Compile times: A one-line change could easily take >10 seconds to compile in dev, constantly shattering flow.

Has anyone else experienced this? I've mostly read comments on how good Elixir is and if you are a Rails user you will only benefit more from Elixir. This is a bit surprising

[ Parent | on HN ]

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by arrowsmith on Friday October 17, 2025 @05:57AM (#45614906)

Not remotely. Maybe I'm just not working on big enough projects, but I've never experienced any frustration at all with Elixir compile times.

[ Parent | on HN ]

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by Kreoss on Friday October 17, 2025 @11:02AM (#45617598)

Nope. I also worked on a Startup with a Full Phoenix LiveView Experience. Codebase was around 300k-400k lines of code and compilation was blazing fast. I would say they have a lot of circular dependencies if they are experiencing that.

[ Parent | on HN ]

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by fridder on Friday October 17, 2025 @11:55AM (#45618193)

for a very large graphql api maybe? I've seen long compiles with a combo of Absinthe, Phoenix, and Elm. Also if you are not a little careful about dependency cycles it can get messy. It is an easy thing to check in CI via mix xref graph --format cycles --fail-above

[ Parent | on HN ]

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by ryanrasti on Friday October 17, 2025 @02:05PM (#45619871)

Ah yeah great callout, that's very plausible. We used Absinthe heavily to power our GraphQL API.

[ Parent | on HN ]