I have doubts about GraphQL. I don't think it indispensable at the future. Instead I think Rxjs and/or Typescript are more important to learn. Maybe they will inluded in JavaScript native.
-
-
-
I personally see GraphQL as the next big standard in API's. Over time I can see it replace REST similar to how REST replaced SOAP. The fact that it's governed by an independent foundation makes that thought even stronger :-)
-
Eh, I disagree. GraphQL seems nice on the surface but gives me flashbacks to SOAP and early AJAX. See: https://medium.com/hotels-com-technology/pros-and-cons-of-graphql-2ec9104c74f2 … Also web technologies, while not going anywhere, are far from the the only or even best way to "stay relevant."
-
Did you ever work with it yourself or do you accumulate your insights through blog posts?
-
What's your preferred style of graphql implementation?
-
I have been using Apollo mostly, also worked with NestJS, Prisma and Hasura. They are all great options that come with pros and cons :)
-
What would you say are the cons of Hasura vs Prisma or others? Seems like interesting tech...
-
I intend to write more about this later, but mainly: Hasura is more lightweight, can be used as the only GraphQL server and basically exposes your whole DB, not un-similar to Firebase. Prisma adds an extra layer in front of your DB so you need to define the layer for the frontend
- 2 more replies
New conversation -
-
-
You might as well start living in a cave right away

-
Tweet unavailable
-
-
That's what you become when you are working with pointers all day...
-
-
Great talk, and awesome speaker. Shows you don't have to feel entitled because of the tech you are using

- 2 more replies
New conversation -
-
-
Sent you the calendar invite to take a look back at this tweet in 10 yearspic.twitter.com/Ew2d9MZdTO
-
Love it!
-
That's, of course, if Google Calendar would still be around in 10 years
(Hopefully it will be
) -
It has been for the last 10 or so... I remember blogging about it but that blog no longer lives
End of conversation
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.
Bram Borggreve - developer
