I'm only familiar with REST and not GraphQL, but this sounds interesting. Just from the name GraphQL sounds like a query language -- how can one do operations that change state (i.e., analogous to PUT/POST) rather than just query it? Thanks.
It’s a QL in the sense that it accepts a client specified schema, that looks how the client wants the data to be returned.
How does it mutate then? SQL can mutate, I’m not sure why this would be any different. Basically, like SQL’s UPDATE, and INSERT, GQL can have “methods” associated with parts of the schema.
It makes it easier to get started, and you can often kinda-ish reuse some effort from your webpage at the cost of bad performance and non-native look/feel.
It's a trade-off for me, I use it when the trade-off feels right.
"The Twelve Kingdoms", by Fuyumi Ono. We'll count all the volumes as one.
Maybe I read them at just the right time in just the right place, but if you are in the right mood it tells you a story about leadership, a kernel of intersectionality, and most importantly why it's so hard for leadership figures to change the way they are headed even if they can clearly see that they are heading straight into an iceberg.
There's also an animated TV-series by NHK that I can recommend.
Because Cycles is a rendering engine, while FireRays is a ray intersection acceleration library. Cycles could opt to use FireRays for ray intersection if they wanted to, but most uses of FireRays probably could never use Cycles since need a rendering engine with entirely different capabilities (real-time &c.)
Write 'normal' text for example, also if you're including CJK-strings in your app it is kind of nice if they are not rendered as teensy or on top of each other.
The main disappointment is that input types are not nearly as expressive as output types.