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

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

#221

Post by dogweather » Tue, Jul 05, 2016, 5:04 PM UTC

vidarh wrote: post #163

neya wrote: post #156

I see a lot of pro-Erlang/Phoenix pushing in here, which is (as a polite reminder) an announcement about the rails framework. Not to say that one shouldn't, just that I think it's deviating from the main topic in hand. Interestingly, I wanted to find out what's the real reason behind these pushes towards Erlang/Phoenix and I realised the discussion is mostly around how you can save a few bucks worth $20-50 by opting…

I personally dislike Rails quite a bit, but I still agree with you. Personally I think the main choice of language and framework for web sites should be down to what you can easily hire developers that will be happy for. I've chosen PHP for that in the past despite detesting it, at a time when Rails did not have enough of an eco-system. I might pick Rails now, even if I personally dislike it. I'd be concerned with ni…

The biggest difference I'm seeking is quality of life.

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

#222

Post by dogweather » Tue, Jul 05, 2016, 5:07 PM UTC

anonyfox wrote: post #162

neya wrote: post #156

I see a lot of pro-Erlang/Phoenix pushing in here, which is (as a polite reminder) an announcement about the rails framework. Not to say that one shouldn't, just that I think it's deviating from the main topic in hand. Interestingly, I wanted to find out what's the real reason behind these pushes towards Erlang/Phoenix and I realised the discussion is mostly around how you can save a few bucks worth $20-50 by opting…

> I see a lot of pro-Erlang/Phoenix pushing in here, which is (as a polite reminder) an announcement about the rails framework. Not to say that one shouldn't, just that I think it's deviating from the main topic in hand. You're right basically, but the migration wave from rails to phoenix has noticeably started, and it shows. > Interestingly, I wanted to find out what's the real reason behind these pushes towards Erl…

Yes, the huge win is developer efficiency and enjoyment. These _can_ make or break a business, for good reasons. They're also the reasons for the initial movement to Ruby and Rails in the first place. Elixir and Phoenix takes it a big step farther.

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

#223

Post by dogweather » Tue, Jul 05, 2016, 5:08 PM UTC

steveklabnik wrote: post #180

anonyfox wrote: post #162

Earlier quoted context omitted.

> I see a lot of pro-Erlang/Phoenix pushing in here, which is (as a polite reminder) an announcement about the rails framework. Not to say that one shouldn't, just that I think it's deviating from the main topic in hand. You're right basically, but the migration wave from rails to phoenix has noticeably started, and it shows. > Interestingly, I wanted to find out what's the real reason behind these pushes towards Erl…

I really like Elixir and Erlang, but haven't found he time to play with Phoenix. But... > You're right basically, but the migration wave from > rails to phoenix has noticeably started, and > it shows. People have previously said this about: * Clojure * Node * Go And lots of things before that.

And therefore, what? :-) You imply a conclusion, but i'd like to know what you believe this implies.

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

#224

Post by dogweather » Tue, Jul 05, 2016, 5:13 PM UTC

davidw wrote: post #144

eric-hu wrote: post #140

Earlier quoted context omitted.

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.

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.

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.

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

#225

Post by dogweather » Tue, Jul 05, 2016, 5:17 PM UTC

ch4s3 wrote: post #5

jesalg wrote: post #3

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

Seriously, .or() always felt like a glaring omission.

I'm pretty sure that DHH strongly opposed .or(), but I'm not sure why. I'd really like to know if this is true, and if so, what the reasoning was.