is this dead ?

[olypros]

Does this gets any update ? any new alternative ?

[skosch]

@ricking06 I don't know the answer to your first question, but one alternative is Absinthe, which is under active development and quite pleasant all around.

[sntran]

@ricking06 Another alternative is https://github.com/shopgun/graphql-erlang, which I like due to its usage of pattern matching (instead of schema modules) and binary keys (instead of atoms).

It's in Erlang, but you should be able to use it directly in Elixir.

[seivan]

I am also curious. I like simplicity of this without resorting too much on Macros and magic.
It makes it clear cut how the entire scheme looks like in the end and I appreciate it.
However docs seem kinda sparse and not how much support it has for channels/sockets/subscriptions yet.

[skosch]

I've been working with Absinthe (and Relay/Apollo on the client side) for a year and a half now, and the one thing I've never had to concern myself with was schemas and macro magic. It just doesn't matter. Your types/schema is something you set up once at the beginning, and then 99% of your time is spent writing resolvers and building your front end. I haven't used graphql-erlang, but Absinthe's documentation, community, and support for all the latest shiny stuff (including subscriptions) are fantastic; if you want something that just works, batteries included, then it's a great choice.

[sntran]

Not all cases have schema at the beginning, at least my case does not. While it's faster and convenience, the dependency on compile-time schema is what keeps me away from Absinthe.

I guess people wanting to know about the status of this project do need the flexibility it provides.

[seivan]

I like the readability of the simple Structs combined together. But Abinsthe does look great and well documented.