I'd say it depends by the nature of your data. In the most cases, REST is just good enough
-
-
Sure, REST is good enough and works perfectly fine, it's just not as nice to use
3 replies 0 retweets 9 likes -
Replying to @mxstbr @kureevalexey and
If I were learning about APIs from scratch I'd skip REST and just go straight to GraphQL, honestly.
6 replies 4 retweets 22 likes -
Replying to @mxstbr @kureevalexey and
That’s ignoring a large portion of the internet, no? I assume most React apps still consume REST APIs, probably good to be familiar with.
1 reply 0 retweets 10 likes -
Replying to @yoniweisbrod @kureevalexey and
Yep, for sure in terms of how to use them! But how to build them?
1 reply 0 retweets 3 likes -
Replying to @mxstbr @yoniweisbrod and
If you'd like to switch deps in your co and they build REST, sure, learn REST! But if you want to do something on your own, why not GQL?
3 replies 0 retweets 8 likes -
Replying to @mxstbr @yoniweisbrod and
You can build a REST API without a framework - just node is enough. GQL needs frameworks, and while perhaps easy they're def not simple
3 replies 0 retweets 3 likes -
Replying to @yoshuawuyts @mxstbr and
try building a GraphQL api with graphql-tools, it's simple AF
1 reply 0 retweets 1 like -
Replying to @thekitze @yoshuawuyts and
Hmm, I don't think it's simple(r) to build one, I think it's easier to use though.
1 reply 0 retweets 0 likes -
Especially around authorization there's lots of holes atm while first people get some real-world usage in.
1 reply 0 retweets 0 likes
Also word has it that posting data is non-trivial. Heard people skip that part and use REST. Idk, don't think it's responsible to recommend
-
-
Replying to @yoshuawuyts @mxstbr and
Agreed. We fetch as it combines resources. Mutations are REST.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.