Hey Bruce, thank you for the fast reply. I agree, that graphql is really "nice" for the client and really "complex" to handle it "nice" on the server (query composition, caching, views integration, maybe? React SSR on top etc.). As I said, for me, Absinthe looks really good. I'll check out your slack chat for some of my questions.
Thx again, Boris Am Montag, 23. Mai 2016 18:27:56 UTC+2 schrieb Bruce Williams: > > Boris, > > (The following speaking as the creator of Absinthe and it's maintainer, > along with Ben Wilson.) > > First of all, thanks for the kind words. > > As you might expect, this has come up. Besides the "name" issue, there's > also the fact that the subject of GraphQL isn't a simple topic, and it's > hard for new users to evaluate solutions adequately. I mentioned as much on > Twitter during ElixirConf EU: > https://twitter.com/wbruce/status/730778840310616064 > > From a technical perspective -- as far as we can see -- there are no > advantages that graphql-elixir currently has over Absinthe. Absinthe is > more complete, faster, checks for more errors (& at compilation time), has > broader production usage, more discussion, better spec coverage, superior > documentation, etc. Our needs to use it in production have really pushed us > to develop features, hammer out bugs, and develop other integrations like > Absinthe.Relay as more than just an item on a checklist. > > The graphql-elixir team and our own are on amicable terms, and we discuss > things regularly -- but as the internals, approaches, and scopes of the > projects are so different, at the current time, there's not a plan to merge > (from our perspective, there's nothing from graphql-elixir that would make > sense to, besides possibly some spec test cases). > > Absinthe is by no means perfect. There is code in the main Absinthe > project itself that could be improved, and there is a long list of features > on our roadmap we would like to implement (projection, query complexity > analysis, deferred queries, etc). We would definitely appreciate help there > and in general, but it seems clear that the graphql-elixir team is going to > continue to work on their separate implementation -- a choice that I think > is completely reasonable for them. > > The question, really, is what the community chooses -- and whether a > "merged" version (even if just team merging) is the way forward. We have no > plans to retire Absinthe's source -- it's a critical production dependency > for us -- and, as I said, it doesn't appear the graphl-elixir team has > plans to close up shop either. In the meantime all that Ben and I can do is > continue to improve Absinthe every day while we support our users and > improve our own production infrastructure. > > Whether the community makes an implicit choice or a specific project makes > an explicit endorsement isn't something we can control, but we're always > open to discussing the comparative benefits of our implementation, and > collaborating on any way we can to better support GraphQL for Elixir > developers. > > If anyone's interested, you can find Absinthe at > http://absinthe-graphql.org, and our Slack chat via > http://absinthe-graphql.org/community > > Cheers, > Bruce (& Ben) > > > > > > On Mon, May 23, 2016 at 8:12 AM 'Boris Kotov' via elixir-lang-talk < > [email protected] <javascript:>> wrote: > >> Hi, I am just coming from the excellent elixir-getting-started curse. >> >>> And I was looking for good graphql implementation in elixir especially >> for the phoenix infrastructure. >> I found that there are two competing projects which are targeting this >> technique: it's the graphql-elixir & absinthe. >> >> So, for a newbie in elixir and phoenix its difficult to make a choice >> between these two. >> I would say, that regarding the documentation feature coverage, absinthe >> feels definitely more promisingly. Good work! >> >> But the graphql-elixir tend to be more popular, why? maybe because the >> most devs choose it as it comes first for the >> www.google.com?q=elixir+graphql query ;) >> And heres my point, there are two teams working on the same issue, and >> competing each other spending energy. Instead of putting their bright minds >> into a solid solution which should be some kind of approved by the >> elixir/phoenix/hex team. (it's my freedom to say it!) >> >> Ok, sorry for the long preamble, here is my question to the graphql >> folks, what do you like on graphql-elixir and absinthe, what are the >> benefits of each? Thank you guys >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elixir-lang-talk" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elixir-lang-talk/89baa490-de92-4972-8333-ef3ca9219b4a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elixir-lang-talk/89baa490-de92-4972-8333-ef3ca9219b4a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-talk/52d5f1ac-1a4e-4814-94c6-cb171b0a4cf2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
