Falcor VS GraphQL

Interesting the article jumps straight from REST to GraphQL and forgets Falcor[0] - Netflix's alternative vision for federated services. For a while it looked like it might be a contender to GraphQL but it never really seemed to take off despite being simpler to adopt. [0] https://netflix.github.io/falcor/. - Source: Hacker News / 7 months ago

- obviously netflix with falcor, EVCache and hundreds of other projects. Source: almost 2 years ago

I pushed for Falcor over GraphQL in 2016. I still think Falcor was a more elegant core idea, but the implementation, tooling, and community never materialized like it did with GraphQL, and now Falcor is relatively niche and obscure. Netflix wasn't willing or able to promote it like Facebook did with GraphQL. That was beginning to be apparent in 2016, but I liked the concept too much. Source: over 2 years ago

Netflix has two amazing aspects I think. One is obviously the movie infrastructure and the other the way they do data and state management. I would read up on https://netflix.github.io/falcor to get an idea what is involved here.to be honest I dont get the point of rebuilding the visual aspects of their web app, that part is trivial and also completely useless without the parts that matter. Source: almost 3 years ago

In this article, I’ll show why GraphQL is the preferred approach over a RESTful API here, demonstrating how to deploy Apollo Server (and Apollo Explorer) to get up and running quickly with GraphQL. - Source: dev.to / 6 days ago

GraphQL is a query language and runtime for APIs. It provides a flexible and efficient way for clients to request and retrieve specific data from a server using a single API endpoint. - Source: dev.to / about 1 month ago

When you use technologies like GraphQL, it is trivial to derive TypeScript types. A GraphQL API is created by implementing a schema. Generating the TypeScript type definitions from this schema is simple, and you do not have to do any more work than just making the GraphQL API. This is one reason why I like GraphQL so much. - Source: dev.to / about 1 month ago

REST and GraphQL have advantages, drawbacks, and use cases for different environments. REST is for simple logic and a more structured architecture, while GraphQL is for a more tailored response and flexible request. - Source: dev.to / about 2 months ago

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications. - Source: dev.to / about 2 months ago