As Elixir and Phoenix are well known now, I think it might be handy to have a thread that lays out differences, benefits and personal experiences that anyone might like to share 
What do you think about add translations to elixir-lang site? I think it will be an additional advantage for novice programmers. If someone is interested I can try translate it to my primary language. 
Go open an issue in the repository, or even send a mail to the core mailing list. But i bet José could be interested
This might be a bit off topic but people always say Railsâ ecosystem is bigger (true). Iâm wondering what Ruby libraries people like to use that donât exist in Elixirâwould love to help out the ecosystem grow and gain parity.
What do you like about Phoenix?
The speed and concurrency.
What do you miss from Rails?
Whatever you may need, there is always a gem for that. Want to do recurring billing with paypal, there is a gem for that. This is one area where Elixir is really lacking.
Where are they similar?
Both the communities are awesome.
When would you use/recommend either?
At this moment if you have to integrate with other products e.g. paypal, Iâd go with Ruby. If the app needs to be performant Iâd go with phoenix. A combination of these could also be a good approach.
Anything else youâd like to share?
It would be awesome if we can talk about ways to use code written in Ruby from Elixir. Be it using ports or message queues.
If you think that this is a good idea to ask I will just ping @josevalim.
I noticed that the biggest difference between these projects is their popularity. So I thought that translate this page can help increase interest of beginners and de facto increase elixir-lang popularity.
I see that elixir-lang page have no option to change language, so I thought there are no plans to introduce this. What do you think about it José?
We would love more translations but not on the main website because that would add burden to us to maintain multiple translations. imagine for example how to handle bug reports and pull requests if we had 10 translations on the same repository.
However, we have recommended others to fork the website, remove the dynamic stuff, like blogs and deploy your translation. I think there are 2 or 3 translations running like that although I canât recall the idioms.
Another idea is to support Elixir School, which seems to have a good workflow for translators and is a great way to get started with Elixir.
Am I the only one who cringes at the âversusâ in the title here?
I donât want to propagate the idea that for one language/framework to grow means that some other has to diminish. Or that a junior developer can pick one to learn and then rest on their laurels for the rest of their career without continual self-education. Always be learning. Try both out if youâre not sure which one fits a situation. At this point of both frameworks, in a given situation, I can imagine choosing/recommending either one.
If I need to summarize my thoughts on the reasons to choose one over the other it is that Rails gives you more short term benefit (from the large community. number of gems, number of blogs, ease of finding knowledgable developers, etc.) at the expense of potential long term scalability bottlenecks (if your app/company survives that long). Personally I prefer a long-term vision, but I do the people paying my paycheck a disservice by only thinking long-term. Phoenix is the better long term solution, but without a team who has used it before, youâll find yourself slower in the short term just learning new ways of thinking and new tools and making beginner mistakes. If your app never needs to scale beyond a level you can get from of Rails out of the box or via blog recipes, then you spent more time than you need to.
5 posts were split to a new topic: Split posts from Rails vs Phoenix thread
IMHO - better interop between Ruby and Elixir would drive adoption and benefit both communities. Elixir could use the Gems. Rails would benefit by consolidating the job-queue and web-socket processes onto the BEAM.
The wording of the title was very deliberate because I feel that 9 times out of 10 people wishing to compare Rails and Phoenix will most probably Google âRails vs Phoenixâ - and I would love for them to be referred here so they will (imo) be more likely to see a well balanced and fair discussion.
If you also object to the post content I would appreciate you telling me how I could do a better job of inviting comments about what people like about Phoenix, what they miss from Rails, where they feel they are similar, where they feel they differ the most, when they might use or recommend either plus anything else theyâd like to share that others might find helpful.
You do not understand me correctly. I do not want to allow bug reports or pull request in other languages.
The main part to be translated is an Elixir tutorial and optionally site UI (links, buttons etc.).
Note also that the copy of page could be confused with an attempt to fraud and therefore deliberately omitted. Am I wrong with it?
Optionally docs could be translated too if collected docs data (function definition, spec and description) would be saved into database.
But basically what I want is to just translate an elixir tutorial.
If I would like to have translated copy of the tutorial the best course would be set up my own page with custom look.
This gives more work than normal translation and in some cases (for example if I want TLD or better hosting) I need to pay for my site.
What do you like about Phoenix?
What do you miss from Rails?
Devise
Take a look at https://github.com/smpallen99/coherence
Channels, use the right tool for the job (asset pipieline, more in the DB, GNU gettext), changesets, explicitness, Phoenix is not your application, raw performance while pretaining general pleasure, View â Template distinction
What do you miss from Rails?
Eco system. Not only gems (something good & stable devise-ish comes to mind), but also integrations for bug monitoring, application performance monitoring and all that. Easy integrations for useful services e.g. relating to payment etc. - in general we found everything we needed though (PostGIS, JWT & friends)
Where are they similar?
Overall MVC structure (although that seems to change) and a focus on developer happiness and productivity and largely a nice community.
Where do they differ the most?
Phoenix is not your application vs. holy monorail of all the things that even inlines perfectly fine library functionality (timecop). Also to the point where Phoenix is more a normal elixir/mix project whereas Rails is⊠a Rails project.
When would you use/recommend either?
Basically Iâd wanna check if:
Anything else youâd like to share?
Thanks for Elixir and Phoenix. Itâs a joy for me and I love it very much although we should avoid the âitâs better than everything else!!!â.
Just gave a talk at Rubyconf.pt about Elixr and Phoenix - people loved it and were very interested 
These tasks are more complex in Elixir, b/c a typical application consists from dozens independent apps. But there is a plenty of projects that provide some opportunities in these areas:
Having suggested coherence in place of devise; what is recommended to fill the authorisation role of pundit?
For those interested in auth, have a look at this thread 
It appeals to me that here is a web server technology that will spread itâs workload across multiple cores working concurrently and do so implicitly without a special rewrite. Low power multicore CPUs (e.g. Octacore ARM) offer high throughput at very low cost. This massively reduces the need to crank up multiple instances as workload rises (in the way cloud providers love to do). This is about Elixir/ BEAM more than Phoenix but they are inextricably linked.
The other comment is that with Rails: background jobs need extra plumbing and often extra external processes that have to be configured and coordinated at every turn. Phoenix by contrast appears to encompass such capabilities without fuss.
We now have a thread (missing libraries and tools) setup to do exactly that.
© Copyright Elixir Forum | Terms | Privacy & Cookies
