RailsConf 2016 - Rails to Phoenix by Brian Cardarella
Why Hacker News recommends it
HN points Rails developers to it as a real-world case for migrating to Phoenix, backed by numbers.
What it is
Brian Cardarella's RailsConf 2016 talk on why and how teams can move from Rails to Elixir and Phoenix. It covers performance gains without losing productivity and how to introduce Phoenix in an organization.
Recommended by 4 HN commenters across 3 different months, 2016 to 2016.
What Hacker News said
Strong rec anonyfox · 2016-07 · on “Rails 5.0: Action Cable, API mode, and more”
I'd say you really should have a look into [this video] . A really great presentation, including numbers and real world backup data, plus conceptual overviews.
Recommends alexgaribay · 2016-05 · on “Ask HN: Fed up with Ruby/Rails; what language should I learn?”
I can't speak about experiences with Ruby/Rails since I don't use that stack but I can give you advice about both Scala and Elixir. I used to be a Java programmer and fell in love with Scala and functional programming. Scala helped me do things that I couldn't do so easily in Java in a more explicit way. However, I found doing web development with Scala to be more cumbersome than helpful but was still a great learning experience for FP in general. Since late 2015, I've been all-in on Elixir. Elixir does everything I wanted to Scala, specifically pattern matching everywhere and how powerful it is. Since Elixir uses BEAM, it's incredibly lightweight but can scale without any configuration. The
Recommends bcardarella · 2016-06 · on “Elixir v1.3 released”
If you're looking for a reason to migrate from a stack like Ruby/Rails to Elixir/Phoenix you should check out my RailsConf talk on that exact subject: [this video]
Recommends tim333 · 2016-06 · on “Elixir vs. Erlang, is Elixir safe bet for my time investment?”
I started watching RailsConf 2016 - Rails to Phoenix by Brian Cardarella [this video] as suggested in some comment yesterday and it has some stuff on whether learning Elixir is worth the time. Good talk in general. Edit link to comment thread: [LINK]
Recommends bcardarella · 2016-06 · on “Phoenix 1.2”
I posted this in the Elixir 1.3 thread but also relevant here. If you're looking to understand why you/your company may want to consider migrating from Rails to Phoenix you can check out my RailsConf talk on the subject [this video]
Recommends bcardarella · 2016-06 · on “Rails 5.0: Action Cable, API mode, and more”
We've moved all of our backend offerings from Rails to Elixir/Phoenix. Despite some questioning the value of anything below 100ms response times there is a lot of data backing up the idea that Elixir/Phoenix can lead to a more maintainable and more economical solution. I spoke about this recently at RailsConf: [this video] Don't get me wrong, I think Rails is an amazing technology but it doesn't fit the use cases and demands our clients have today.
Cites anonyfox · 2016-07 · on “Rails 5.0: Action Cable, API mode, and more”
> but Erlang/beam code is not that fast. True, no doubt. You wanted a comparison why phoenix is faster than rails. And simply doing things at compile time reduces work at runtime. In Ruby, all Metaprogramming must be done at runtime, for example via method_missing trickery (been there, done that). > Ruby's templates are parsed into code that stays in memory, too, so it's not like they're re-parsed each and every time. This is actually not the same. A single immutable blob of binary (elixir strings) which is shared throughout the whole application can leverage hardware caching better. Jose could answer this probably better than I can do. > someone should dissect these things in a real-world-i