Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

Re:Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo by schneidmaster on Sunday April 21, 2019 @08:01PM (#19715338)

It's 100% the syntax. It appeals to ruby devs and also I think it's a lot easier to grok in general. But you can write Erlang code directly in an Elixir file, you can use Erlang libraries directly in Elixir, and Elixir compiles to the same BEAM instructions that Erlang does, so there's functionally no difference in terms of capabilities or what happens when they run.

[ Parent | on HN ]

Re:Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo by SteveGregory on Sunday April 21, 2019 @08:18PM (#19715412)

This is not totally true. It’s not 100% syntax. Elixir has one additional and widely used feature: macros.

In Elixir, as in Lisp, you can transform your code as a data structure into new code. This is importantly used in Ecto, the de-facto object data mapper in Elixir. It’s also used in Absinthe, a library from the posted link for making GraphQL APIs.

[ Parent | on HN ]

Re:Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo by ramchip on Sunday April 21, 2019 @09:42PM (#19715763)

Protocols are also an important feature. `IO.inspect`, `Enum`, etc. are very nice additions.

[ Parent | on HN ]

Re:Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo by elcritch on Sunday April 21, 2019 @09:59PM (#19715821)

In general the standard library organization is superb and well laid out. It’s the only language I don’t have to consistently lookup "how do I do X with string", or “Y with a list".

[ Parent | on HN ]

Re:Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo by schneidmaster on Sunday April 21, 2019 @08:46PM (#19715528)

Yeah, this is fair. I was mentally lumping certain language features under "syntax" but that's not really accurate.

[ Parent | on HN ]

Re:Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo by out_of_protocol on Monday April 22, 2019 @03:11PM (#19721845)

* consistent standard library (huge win IMO)

* efficient utf8 binary strings (which is actually conforms with utf8 standard), no mixup with charlists

* mix etc standard tooling

* macros

* enum stuff

* pipeline operator "|>", which by its mere existence enforces input/output param's consistency in user-written functions

etc

[ Parent | on HN ]

Re:Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo by qaq on Sunday April 21, 2019 @08:03PM (#19715346)

well better unicode support too

[ Parent | on HN ]