Hacker News Reader

Thought the same. Strict typing allows many optimisations and compressions. Without strict types most of graphQL has no benefits anymore.

I second this. Currently with the right tooling and IDE extension, I can get autocompletion and various compile-time checks with GraphQL schemas.

I'm not saying it is negative. Probably I should not color red the background in the table.

I just wanted to point out where jrGQL is different from others.

Just knowing which fields are nullable, that's already a surprisingly huge productivity boost.