Edit: Nevermind, this has already been answered. Anyone have insight on relay modern vs apollo? http://www.apollodata.com
For anyone that comes along, I answered in this comment: https://news.ycombinator.com/item?id=14143112
Relay Modern: Simpler, faster, more extensible
71–80 of 111 posts
Re: Relay Modern: Simpler, faster, more extensible
#72It seems many people loved GraphQL, a powerful and elegant concept, but then had a rude awakening with Relay as an overly complex, unwieldy, buzz kill.
Node, edge, and viewer are terrible mistakes w.r.t. naming and usability. I'm sure it's very intuitive for FB devs to think in these terms, but the words are specific to a problem domain and just don't translate as well to the general case as other choices might have.
Re: Relay Modern: Simpler, faster, more extensible
#73Congrats! Relay is what really sold our iOS-only native team to move to React Native. Very excited to migrate to modern version at some point in the future. ( http://artsy.github.io/blog/2017/02/05/Retrospective-Swift-a... )
is emission the only react-native app artsy has built/open sourced?
Yes, it's the only React native we have apart from trivial demo apps to prove a concept (which stay on a user's repo rather than the artsy org )
Re: Relay Modern: Simpler, faster, more extensible
#74It seems many people loved GraphQL, a powerful and elegant concept, but then had a rude awakening with Relay as an overly complex, unwieldy, buzz kill. Node, edge, and viewer are terrible mistakes w.r.t. naming and usability. I'm sure it's very intuitive for FB devs to think in these terms, but the words are specific to a problem domain and just don't translate as well to the general case as other choices might have.
That was one of the reasons I ran as fast as possible to Apollo after trying to understand Relay for a bit (that and more or less no tutorials for Relay). The other one was that Relay seems to be one of these "my way or the highway" frameworks, while I prefer libraries which follow my needs and don't force me to do all things the way they want.
Re: Relay Modern: Simpler, faster, more extensible
#75I've been somewhat out of the Clojurescript loop recently, but this looks conceptually a lot like the om.next model ("colocated queries").
Makes me curious how many people are using om.next in anger. It's always seemed like a good idea (and now with some extra endorsement for the core principle), but judging by GitHub activity (which I realise isn't a perfect measure), the project seems to have rather lost momentum.
Re: Relay Modern: Simpler, faster, more extensible
#76I work at Facebook and had the chance to use Relay Modern for an upcoming product. Was really happy with the performance and collocation of data and view just amazing. Love it :) BTW I realized where Relay's logo came from by chance while fiddling around with PowerPoint's new Morph transitions... https://gfycat.com/EnviousBothFinch
Re: Relay Modern: Simpler, faster, more extensible
#77Earlier quoted context omitted.
> the day when Facebook gives up on flow and adopts Typescript will be a glorious, glorious day. I foresee FB to skip TypeScript and go straight with ReasonML[0], as 25%[1] of the messenger code base supposedly is already converted to Reason. And I think that is even more glorious development then FB going with TypeScript. :) [0]: An easier to approach (for programmers coming from mainstream languages; like JS/C++/Ja…
BuckleScript is by Bloomberg, specifically https://github.com/bobzhang , not Jane Street. The developer of js_of_ocaml, the other JS to OCaml compiler, works at Jane Street though.
Oops, sorry. Cannot edit anymore. So please everyone read this!
Re: Relay Modern: Simpler, faster, more extensible
#78One of the things that I've noticed about the javascript community is that they're re-inventing stuff from previous technologies - sometimes badly - but almost always with a willful ignorance of what has gone before.
While this doesn't look like a bad idea - what they've done is to re-invent stored procedures. Back in the original object orientated wars this turned out to be a mixed blessing. You could get quite sharp performance, but reasoning about the application logic became harder. It might be nice if this kind of issue was at least acknowledged in the article.
Re: Relay Modern: Simpler, faster, more extensible
#79Earlier quoted context omitted.
Here is a detailed comparison between Apollo and Relay: https://www.graph.cool/docs/tutorials/relay-vs-apollo-iechu0... (Note: This article hasn't been updated for Relay Modern yet but the main points are still the same.)
I think the comparison is going to be pretty different for Modern because Relay Modern has some significant changes in the approach.
You're absolutely right, we're already working on an updated version. We'd love to have Apollo's feedback on it to make it as helpful as possible!
Re: Relay Modern: Simpler, faster, more extensible
#80Seriously, your own homegrown garbage collection inside the js runtime? I looked at React the first time it came out and aside from the insanity of using xml mixed with javascript or some kind of pseudo js, it was waaaay too complex. I dont know but it seems crazy to me to write applications like that, it makes xaml look decently simple.