Remember when ORM seemed like a great idea?
-
-
Yeah, though it’s also changed a lot in the last 5 years.
-
@floydophone remember when we had to write code like this?


pic.twitter.com/SVEWvbDxFU
-
This was a great talk that I’d never seen before. Interesting to know the history.
-
@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
-
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?
-
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. -
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.
- 4 more replies
New conversation -
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.
Tell us more , please!