Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity • Hacker News Board

Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity

#11

Post by nullstyle » Mon, Dec 12, 2016, 9:36 PM UTC

mfb2 wrote: post #8

brightball wrote: post #5

Earlier quoted context omitted.

The main use case would be if you had a very mature Ruby library without an Erlang/Elixir equivalent. I haven't run into much that I personally need that isn't already available, but there are definitely some gaps that this could help people jump in the short term.

Agreed. Currently working with a host of legacy ruby projects that we're slowly migrating to elixir. We've used hack-arounds to leverage the existing ruby projects up until now. If this library proves to be production-worthy, it'll be a great bridge for addressing some technical debt.

Erlectricity, from what I understand, was used extensively in at least one iteration of github's architecture. It has spent a lot of time in production deployments.

Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity

#12

Post by felideon » Mon, Dec 12, 2016, 10:04 PM UTC

arcaster wrote: post #3

I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework, however, I'm curious what the advantage or use-case of having Ruby talk to Elixir in an application is?

> I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework?

Could you explain why, at least as it pertains to web development?

As a (former) Common Lisp developer I find Ruby on Rails suffices for the vast majority of needs, and believe its popularity and maturity pays off in productivity gains.

Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity

#13

Post by phamilton » Mon, Dec 12, 2016, 11:02 PM UTC

felideon wrote: post #12

arcaster wrote: post #3

I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework, however, I'm curious what the advantage or use-case of having Ruby talk to Elixir in an application is?

> I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework? Could you explain why, at least as it pertains to web development? As a (former) Common Lisp developer I find Ruby on Rails suffices for the vast majority of needs, and believe its popularity and maturity pays off in productivity gains.

The biggest gap in Rails is websockets. There's just nothing close to ease of use that Phoenix has in that regard. I have not, however, done much with action cable. I don't feel much desire to do so since Phoenix exists.