Re:Reasons to use Phoenix instead of Rails
by sergiotapia on Sunday November 26, 2017 @10:17PM
(#15784564)
It's underhyped because the concepts Elixir brings to the table are most likely alient to most Rails developers (myself included at the time!)
Most people think it's about a faster activerecord, it's not. It's so much more!
Re:Reasons to use Phoenix instead of Rails
by regulation_d on Monday November 27, 2017 @12:59PM
(#15789408)
I really like Ecto for several reasons, but mostly because it makes every database call super obvious. If you Repo.something(), you're probably hitting the database.
A couple other reasons I like it: 1. It's makes shooting yourself in the foot with N+1 queries really difficult. 2. It's not married to Phoenix. I haven't tried this in a while and maybe this isn't representative of the current state of things, but last time I tried to use AR in a non-Rails project, I ended up switching to Sequel gem.
For a nice, if not slightly biased, comparison of AR and Ecto, I recommend Darin Wilson's talk "Thinking in Ecto"[0].
Re:Reasons to use Phoenix instead of Rails
by itbeho on Sunday November 26, 2017 @07:33PM
(#15783964)
I’m old enough to remember when people said Rails was overhyped:)
Hype aside, I really like Phoenix a lot.
Re:Reasons to use Phoenix instead of Rails
by mmanfrin on Sunday November 26, 2017 @08:08PM
(#15784073)
For what it's worth, this submission is a comparison of Phoenix -- a framework explicitly inspired by Rails and which has some core members who were/are Rails core members -- and Rails.
Re:Reasons to use Phoenix instead of Rails
by potatocannon on Sunday November 26, 2017 @09:16PM
(#15784347)
I had similar thoughts initially. After understanding erlang's OTP concepts, it all became clear. Phoenix's simplicity combined with the power of erlang&otp is fantastic.
Re:Reasons to use Phoenix instead of Rails
by 549362-30499 on Sunday November 26, 2017 @06:54PM
(#15783795)
Mind linking me that article about dumping Go for Node.js? I'd love to hear the reasoning behind that!
A few years ago, I remember that all these articles kept popping up about people switching from Node.js to Go.
Now it's funny because fairly recently I read a well thought out article on HN encouraging developers to dump Go for Node.js... These days you hardly read anything about Go at all. Not that there is anything wrong with it, but reality caught up with the hype and it's no longer pretending to be a silver bullet.
Right now Phoenix is pretending to be a silver bullet, but it's really not.