Rails 5.0: Action Cable, API mode, and more

Post by cutler » Fri, Jul 01, 2016, 3:27 AM UTC

bratsche wrote: post #118

cutler wrote: post #92

Earlier quoted context omitted.

Elixir has no native array syntax nor any array functions in the stlib so arrays are basically second class citizens rather than completely absent. Ask not why I need them but why anyone might need them if the Elixir is supposed to be a general purpose language. Why does Clojure need them or Ruby or Python (lists)? If I want to process data as a large indexed array Elixir isn't going to help me and some Elixir devs h…

> Elixir has no native array syntax nor any array functions in the stlib There is no native array syntax, but there are array functions in the stdlib: http://erlang.org/doc/man/array.html

Post by cutler » Fri, Jul 01, 2016, 3:30 AM UTC

tbrooks wrote: post #111

cutler wrote: post #85

Concurrency aside, why is Elixir preferred over Ruby when it doesn't even have a native array implementation? No, lists and tuples are no substitute nor are maps with numeric keys as Jose has suggested. If you want an array in Elixir your only option is Erlang's implementation which ain't pretty - http://erlang.org/doc/man/array.html . When I raised this issue in the mailing list and on IRC the response was invariabl…

In all your replies, you haven't given concrete example of "I need arrays because tuples or lists can't do X". Complaining in the abstract isn't helpful. If Elixir had arrays, why would that be better than using other enumerables like lists or tuples?

Post by Scarbutt » Fri, Jul 01, 2016, 4:05 AM UTC

rdtsc wrote: post #94

rebelidealist wrote: post #83

Earlier quoted context omitted.

That saving of $150 is equivalent to one hour of pro dev work time. It's hardly worth converting unless Elxir / Phoenix is much more productive and maintainable.

> That saving of $150 is equivalent to one hour of pro dev work time. Fair point, unless you have more customers. Then it can start to add up quickly. And by customers it means requests as well. Being able to handle large traffic spikes and continous connections is a game change from what I found. Moreover. A huge benefit is using the BEAM VM, I use Erlang (but same VM) and I have seen major advantages being able to…

Post by perishabledave » Fri, Jul 01, 2016, 4:25 AM UTC

davidw wrote: post #52

bratsche wrote: post #51

Earlier quoted context omitted.

I'm still fairly new with Elixir/Phoenix (as I think most of us still are), but so far I feel intuitively that it's more maintainable and I admit that I don't have the experience or numbers to back that up yet. There are some things that you simply must use other tools for in Rails, because it can't maintain state like Erlang can. Once you start adding in these other things, you're no longer just a "Rails app" but yo…

I would love to see someone take a deep dive into why their Phoenix thing is "so much faster" than with Rails. I mean really look at the whole stack from the VM, to different pieces of the framework like views and DB interaction. Erlang definitely does concurrency well, but it is not that much faster than Ruby in terms of "raw speed". I'd be fascinated to see someone actually do the work and look at where Phoenix is…

Post by epidemian » Fri, Jul 01, 2016, 4:25 AM UTC

jeremyevans wrote: post #130

Raticide wrote: post #71

Earlier quoted context omitted.

This falls apart when you need multiple scopes as it can't tell how to group the 'AND' and 'OR's. The new Rails syntax avoids this problem.

That isn't a problem in Sequel, as you can pass a complex expression to #or, in which case it works as you would expect it to: Post.where(id: 1).or(Sequel.&({:id=>2}, {:name=>'Foo'})) # SELECT * FROM posts WHERE ((id = 1) OR ((id = 2) AND (name = 'Foo')))

  # Using the a "virtual row" block:
  Post.where(id: 1).or{(id =~ 2) & (name =~ 'Foo')}

  # Or, if you don't fancy that kind of block magic, simply passing a Hash, 
  # the same way as with .where
  Post.where(id: 1).or(id: 2, name: 'Foo')