2 ms·
Seems to me like the article and Relay are broken. 1) Why the new declarative query language for fetching attributes (columns) from objects (tables)? 2) Why b
by falcolas 11y ago
Seems to me like the article and Relay are broken.
1) Why the new declarative query language for fetching attributes (columns) from objects (tables)?
2) Why build yet another transport mechanism on the top of HTTP, when there are so many to choose from already?
3) Oh, my god, boilerplate everywhere! What is this, Java?! /s
Seriously, though, the OP has some serious issues with Facebook, but to be fair Relay stinks badly of NIH. They had great success with React (a love letter to PHP), followed that with Flux (more of a design pattern than anything else), but this third attempt seems like it's trying too hard to create yet another data transport system.
- drcode 11y ago> Why the new declarative query language for fetching attributes (columns) from objects (tables)? SQL isn't very composable- It was the right idea, but there's been a lot of progress in the last 50 years on how to traverse a database. It is all string-based, and it lacks a "pull syntax" (i.e. after the query completes, give me this graph-represented chunk of the result) > Why build yet another transport mechanism on the top of HTTP, when there are so many to choose from already? Relay is mostly agnostic on what mechanism is used to fetch results. > Oh, my god, boilerplate everywhere! What is this, Java?! /s Yeah, it's kind of awkward to do this stuff in Javascript- Look at what people are doing in more flexible languages, like here https://github.com/omcljs/om/wiki/Quick-Start-%28om.next%29 https://github.com/omcljs/om/wiki/Quick-Start-%28om.next%29