Rails 5.0: Action Cable, API mode, and more • Hacker News Board

Re: Rails 5.0: Action Cable, API mode, and more

#11

Post by jfaucett » Thu, Jun 30, 2016, 10:29 PM UTC

themgt wrote: post #7

Looks like a solid and and relatively straightforward upgrade from Rails 4.2. It's hard not to feel Rails has become a bit of a slow-moving behemoth though, with this release four years after 4.0. I've still got a couple clients using 3.2 from 2012 and things aren't that different. Smart money at this point seems like a significant portion of the Rails community could begin moving to Elixir/Phoenix over the coming ye…

unfortunately, i agree with you. Ive moved to elixir for all web work and the erlang vm just blows ruby out of the water at restapi/web services stuff. Im a huge ruby/rails fan though, and have earned a living off the ruby ecosystem. I just dont see how ruby can overcome the vm disadvantage to be honest, though id really like to see them try

Re: Rails 5.0: Action Cable, API mode, and more

#12

Post by desireco42 » Thu, Jun 30, 2016, 10:29 PM UTC

A long awaited release is finally here, Yoohoo!

Now, let the job of upgrading begins.

Also, I love how everyone found a feature they've been waiting for and celebrating it. Rails, always bring joy (pain comes in few years ;) )

Re: Rails 5.0: Action Cable, API mode, and more

#13

Post by justinzollars » Thu, Jun 30, 2016, 10:30 PM UTC

I wish I had API mode 4 years ago

Re: Rails 5.0: Action Cable, API mode, and more

#14

Post by [deleted] » Thu, Jun 30, 2016, 10:30 PM UTC

[deleted]

Re: Rails 5.0: Action Cable, API mode, and more

#15

Post by Scarbutt » Thu, Jun 30, 2016, 10:35 PM UTC

jfaucett wrote: post #11

themgt wrote: post #7

Looks like a solid and and relatively straightforward upgrade from Rails 4.2. It's hard not to feel Rails has become a bit of a slow-moving behemoth though, with this release four years after 4.0. I've still got a couple clients using 3.2 from 2012 and things aren't that different. Smart money at this point seems like a significant portion of the Rails community could begin moving to Elixir/Phoenix over the coming ye…

unfortunately, i agree with you. Ive moved to elixir for all web work and the erlang vm just blows ruby out of the water at restapi/web services stuff. Im a huge ruby/rails fan though, and have earned a living off the ruby ecosystem. I just dont see how ruby can overcome the vm disadvantage to be honest, though id really like to see them try

I just dont see how ruby can overcome the vm disadvantage to be honest

I don't know how mature it is, but couldn't jruby be the answer to this?

Re: Rails 5.0: Action Cable, API mode, and more

#16

Post by bcardarella » Thu, Jun 30, 2016, 10:39 PM UTC

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: https://www.youtube.com/watch?v=OxhTQdcieQE

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.

Re: Rails 5.0: Action Cable, API mode, and more

#17

Post by [deleted] » Thu, Jun 30, 2016, 10:40 PM UTC

themgt wrote: post #7

Looks like a solid and and relatively straightforward upgrade from Rails 4.2. It's hard not to feel Rails has become a bit of a slow-moving behemoth though, with this release four years after 4.0. I've still got a couple clients using 3.2 from 2012 and things aren't that different. Smart money at this point seems like a significant portion of the Rails community could begin moving to Elixir/Phoenix over the coming ye…

[deleted]

Re: Rails 5.0: Action Cable, API mode, and more

#18

Post by cortesoft » Thu, Jun 30, 2016, 10:43 PM UTC

jesalg wrote: post #3

This has been long awaited: Post.where('id = 1').or(Post.where('id = 2'))

I like the sequel gem's syntax even better: Post.where(:id => 1).or(:id => 2)

Re: Rails 5.0: Action Cable, API mode, and more

#19

Post by davidw » Thu, Jun 30, 2016, 10:43 PM UTC

bcardarella wrote: post #16

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: https://www.youtube.com/watch?v=OxhTQdcieQE Don't get me wrong, I think Rails is an amazing technology but i…

> more maintainable

I get that the Erlang VM is really nice for some things (I made my first contribution to it in 2004!), but I'm curious about the above statement, as I haven't had the time to dig into Elixir/Phoenix yet.

Re: Rails 5.0: Action Cable, API mode, and more

#20

Post by mmanfrin » Thu, Jun 30, 2016, 10:43 PM UTC

ghayes wrote: post #6

bratsche wrote: post #4

This is pretty cool. I've kind of moved on to Elixir and Phoenix for my web stuff these days, but it's still nice to see Rails going strong.

Been using Elixir / Phoenix as well, and it's been a breath of fresh air. That said, I'm glad that rails has been looking at projects like Phoenix for inspiration as it continues to grow and adapt.

  I'm glad that rails has been looking at projects like Phoenix for   
  inspiration

Other way around.

Phoenix was explicitly inspired by Rails and founded by Rails core members. Elixir was first created by a Rails core member. Phoenix is the performance-really-matters successor to Rails.