Why Astronomer is Betting on GraphQL
astronomer.io
Why Astronomer is Betting on GraphQL
1–10 of 38 posts
Re: Why Astronomer is Betting on GraphQL
#2I hope one of them is "I like the legal risk that comes with exposing myself to patent trolling": https://medium.com/@dwalsh.sdlr/using-graphql-why-facebook-n...
Re: Why Astronomer is Betting on GraphQL
#3Same as React: do not use if you plan to do anything that Facebook might dislike or steal, or want to sell your startup, or work in a bigger corp (ask the legal guys before).
Re: Why Astronomer is Betting on GraphQL
#4Same as React: do not use if you plan to do anything that Facebook might dislike or steal, or want to sell your startup, or work in a bigger corp (ask the legal guys before).
This advice makes no sense for GraphQL, which is a _protocol_ rather than a piece of software. In fact, the perhaps most-used GraphQL implementation these days (Apollo) is not written by Facebook and is purely MIT-licensed.
Of course, you do need to ask yourself these legal questions if you use Relay.
Re: Why Astronomer is Betting on GraphQL
#5I'm the one suffering right now from graphql hype. The idea is great, but it's very immature. Android client is just not ready for something bigger then few simple queries. iOS client is also years behind JS client. If your platform is not limited to JS, It doesn't worth migration. We fighting with custom mutex and other painful tricks to make it working.
Re: Why Astronomer is Betting on GraphQL
#6Betting on ... Great for blog posts, but not great for productivity.
You should blog in a year about: why we migrated from GraphQL to Postgress ( if it's that immature as i see in the comments)
Re: Why Astronomer is Betting on GraphQL
#7Facebook keeps coming up as the evangelist for GraphQL but didnt they move AWAY from FQL in 2015?
Re: Why Astronomer is Betting on GraphQL
#8Same as React: do not use if you plan to do anything that Facebook might dislike or steal, or want to sell your startup, or work in a bigger corp (ask the legal guys before).
This advice makes no sense for GraphQL, which is a _protocol_ rather than a piece of software. In fact, the perhaps most-used GraphQL implementation these days (Apollo) is not written by Facebook and is purely MIT-licensed. Of course, you do need to ask yourself these legal questions if you use Relay.
The major Apollo libraries depend on Graphql.js, which is affected by the patent grant.
Apart from that GraphQL is the only one library with a known patent by Facebook, so you would actually want to get the patent grant there.
[0]: https://github.com/apollographql/react-apollo/blob/master/pa...
[1]: https://github.com/apollographql/apollo-server/blob/master/p...
[2]: https://github.com/apollographql/apollo-client/blob/master/p...
Re: Why Astronomer is Betting on GraphQL
#9Betting on ... Great for blog posts, but not great for productivity. You should blog in a year about: why we migrated from GraphQL to Postgress ( if it's that immature as i see in the comments)
GraphQL isn't really comparable to Postgres. It is more of an alternative to using a REST api.
Re: Why Astronomer is Betting on GraphQL
#10Betting on ... Great for blog posts, but not great for productivity. You should blog in a year about: why we migrated from GraphQL to Postgress ( if it's that immature as i see in the comments)
You cant migrate from GraphQL to Postgress. The two technologies cant possibly replace each other - either way.