-
-
Replying to @floydophone @sophiebits and
@floydophone remember when we had to write code like this?


pic.twitter.com/SVEWvbDxFU
1 reply 0 retweets 3 likes -
Replying to @schrockn @floydophone and
This was a great talk that I’d never seen before. Interesting to know the history.
2 replies 0 retweets 1 like -
Replying to @skevy @floydophone and
@skevy You can see the genesis of GraphQL in this slide. The first version of GraphQL was essentially layering serialization, a type system, and a language over this API. The core runtime was pretty thin, because in effect it was already written.pic.twitter.com/hZidlzg1Ts
2 replies 3 retweets 7 likes -
Replying to @schrockn @floydophone and
Definitely! I noticed this right away when I watched the talk. How much different is the API today? I presume it uses generics because Hack, but other than that is Ent still reasonably similar to its original version?
1 reply 0 retweets 0 likes -
Replying to @skevy @floydophone and
I'm assume totally different. Old abstractions written under totally different constraints; underlying language (async/await!!!) and runtime replaced. I'm sure new engineers roll their eyes at old code and want to rewrite it, as it should be.
@dlschafer would know more than I.2 replies 0 retweets 1 like -
AFAIK we don't really have an equivalent way to fetch deep nesting – partly due to GraphQL, partly because we colocate data fetching with rendering logic (i.e., fetching data in our XHP components' render methods) so each piece of code tends to only need to fetch one layer.
2 replies 0 retweets 2 likes -
Replying to @sophiebits @schrockn and
We do now use a LINQ-style API that lets you do multi-hop fetches but it also isn't really the same use case as the quoted image.
$author = await $question ->queryAnswers() ->queryAuthor() ->genOnly(); await$author->genProfilePic(PicSizeConst::SQUARE);1 reply 0 retweets 3 likes -
Replying to @sophiebits @skevy and
Funny enough the original (untyped, worse) version of that API (EntQuery) was the result of me and
@ola copying as much of LINQ as possible without altering the underlying programming language.1 reply 1 retweet 6 likes -
If you come visit you might see this in the bathroom this week. ;)pic.twitter.com/KzNn8DPl0s
4 replies 1 retweet 6 likes
EntQuery was sold to me 6 years ago for the exact same reasons! :P
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.