HN Theater @HNTheaterMonth

Yeah, in the GraphQL lectures the FB presenters basically said. [1] Watch the first ten minutes if nothing else.

React = the view layer.

GraphQL = the store.

Relay = the glue.

I'm still ambivalent on this form of stack but it's a move in the right direction. Component composition makes JS a lot less messy. Meteor is doing something real interesting with isomorphic JS, and whether or not it gets widespread adoption, I'm happy that avenue is being explored as well. Stefan Richter is doing some REAL interesting work with isomorphic Clojure [2] in his shop in Germany, that has some real interesting exercises. The talk is from 2010, so it was more novel when I first watched it than you'd think of today.

[1] https://www.youtube.com/watch?v=9sc8Pyc51uU [2]

take a look at GraphQL https://www.youtube.com/watch?v=9sc8Pyc51uU it definitely solves design issues with RESTful APIs

Here's the video introducing it at React.js conf: https://www.youtube.com/watch?v=9sc8Pyc51uU

https://www.youtube.com/watch?v=9sc8Pyc51uU - there are some examples in the talk from React JS Conf.

We haven't yet finalized what API we will provide when we open source Relay. You'll certainly get one object, called Relay, however ;)

⬐ Touche

I'm not watching a 30 minute video to get an idea of what writing code in this framework will look like. Can you really not give a single code example, even if the API is in a fluid state?

⬐ underwater

Application code will look like regular React components. The only difference is you declare what data you want in a GraphQL fragment.

Here's a photo from the presentation that shows an example: https://twitter.com/devonbl/status/560532680513556481.

⬐ UberMouse

If they can pull off what they're saying they can, this will be mind blowing. Pretty interested in seeing what the server code for this looks like.

⬐ rcsorensen

The title is burying the lede.

Facebook is talking here about "Relay", a framework around React that handles pulling together all the data needs for a deeply nested component tree, from fetching, to optimistic updates, through error handling and pagination.