nullxone

Taking a puupy’s life increases the net suffering. In a purely ethical world, a world where the AI succeeds.

A world where every life, even a dogs life is different f value.

Can the path to a solution exclude the solution itself.

Here's a 30 second tl;dw: The first two code samples explain the idea. https://hasura.io/blog/how-to-convert-typescript-types-to-gr...

Github repository that powers the typescript function to Hasura connector bit: https://github.com/hasura/ndc-typescript-deno

Building an app or API without a supergraph is like storing your data in files instead of a relational database.

When you treat your graph like a set of nodes, you miss the point of GraphQL.

...leads to the common impression that building out a GraphQL API is busy work... And moreover, this is true! This way of doing things sells GraphQL short.

...serious GraphQL users like Meta and Netflix have their own entity based frameworks to construct supergraphs.

Building an app or API without a supergraph is like storing your data in files instead of a relational database.

Thanks. A lot of these things ring true in a very practical sense.

GraphQL keeps getting more mature and adding more and more tooling/features/middleware, but we also need to work on de-risking the technology from a more fundamental perspective to get to a rock solid foundation.

GraphiQL Alternative from Grafbase

Except extreme chemical addiction, made worse by the fact that the other side effects aren't there to warn your body?

Isn't GABA downregulation the main reason for extreme withdrawal with alcohol?

Lightning has been around for more than 10 years. Now customers can't reuse those cables / accessories. Though I'm sure plenty will welcome the consolidation as well. So the narrative is good for Apple.

Also the facts show Apple lobbied against usb c in the EU: innovation and patents, phone too thin.

Why and how Relay can help scale complexity, focused on scaling frontend teams, compared to other patterns/tools.

The client has a better idea than the server of what should be null in a graphql call.

This is available in Relay today and is coming up as a graphql RFC.

Looking back over different patterns shows how projects and teams should be organised to scale complexity, and how new tech like React Server Components and Backend for Frontend should be used.

Some ideas from the post: BFF should be outside the security boundary (so it can be owned by product teams) RSC is a view layer! Don't put business logic in it.

"There are trillions of searches on Google every year. In fact, 15 percent of searches we see every day are new"

Here's all the things. https://djcordhose.github.io/flow-vs-typescript/flow-typescr...