Rails 5.0: Action Cable, API mode, and more

Re:Rails 5.0: Action Cable, API mode, and more by eric-hu on Friday July 01, 2016 @12:52AM (#12013954)

From what I've read in the comments so far, you won't see it thinking in terms of speed of Erlang vs Ruby. It sounds like the gains come from baked in behavior, so that "Rails + Redis" or "Rails + Redis + nginx" is equivalent to Phoenix alone. I'm still only reading about this, though. No Elixir experience here.

[ Parent | on HN ]

Re:Rails 5.0: Action Cable, API mode, and more by davidw on Friday July 01, 2016 @01:28AM (#12014055)

Erlang definitely does a lot out of the box without needing to rely on other systems and that's a great thing, but we're hearing claims about "fast" and "more maintainable" and I'd like to see more details.

I used Erlang at the last place I worked and like it a lot, but Rails is pretty good too in my book.

[ Parent | on HN ]

Re:Rails 5.0: Action Cable, API mode, and more by dogweather on Tuesday July 05, 2016 @01:13PM (#12037952)

For me, it's "fast" meaning developer time. A typical first pass at a Rails view might be 300ms vs. 300 micro secs in Phoenix. This extra headroom represents hours of optimization I don't need to do, in order to stay under 200ms per request.

[ Parent | on HN ]