V5's database queries are much simpler and more performant than in V4 (which was already faster than traditional execution methods!) thanks to offloading work from Postgres to the Grafast planning engine in Node. I'm so happy that what started out as a theory is now having such measurable impact!
That's amazing! I'm so happy to hear that! Do send me the numbers if you want, I'd love to know specifics. And if you ever have some outliers that go the other way I'd love to help fix it 🛠️
Thanks for the kind words, Paul - and of course for your work in ReScript! We've quite a few in the community that use it from what I hear in the chat, and never a bad word spoken!
I've been using postgraphile for years at work, including latest V5 RCs and it's just a pure gem, very fast and extremely flexible, plus it works perfectly with rescript-relay! Kudos @benjie.dev for the great work!
Thanks Chandler! It's certainly been a head-scratcher at times, and I went down the wrong path more than once, but I couldn't be happier with where we've landed - it just feels right! And there's so many things I'm excited to build on it!
It would be hard to understate how large of a feat of engineering this was. PostGraphile is such a powerful tool and it's great to see such a great foundation for the future in v5
Kudos to @benjie.dev, Jem, and all who contributed to Postgraphile
GraphQL error handling driving you nuts?
@benjie.dev shows a cleaner path by explaining how nulls, errors and schema design should really work together.
Read it here: benjie.dev/graphql/errors
#GraphQL #APIs
It’s super annoying and incredibly verbose; and half the text is nonsense. Send me your prompt, I can run it through AI myself if I want!
Yesterday was the #GraphQL primary working group and I made a presentation about @benjie.dev capabilities proposal.
Slides (cute kittens included!) below.
docs.google.com/presentation...
I really need to get around to seeing if socket.dev produces less noise.
"HIGH PRIORITY VULNERABILITY" screams Snyk.
"DIRECTORY TRAVERSAL!"
Tell me more...
"Introduced through: pg-sql2@2.2.3 › @types/pg@7.4.14 › @types/pg-types@1.11.4 › moment@2.22.2"
Unless I'm severely mistaken how Definitely Typed works, I'm pretty sure that's not an exploitable vulnerability.
The debate over “queries” vs “operations” vs “documents” is separate; but you’re persisting a document (containing at least one operation which may or may not be a query, plus any of their required fragments); thus “queries” is a misnomer & “operation” limits to docs with exact one op unnecessarily
Persisted documents: send identifier rather than entire document (network optimisation)
Automatic persisted queries: ad-hoc persisted documents via optimistic runtime negotiation
Trusted documents: persisted documents used as an allowlist, where persistence signifies trust (security & speed)
Great post from Jovi here! Remember:
Trusted Documents: if you can, you should!
Matt Mahoney has been discussing "generic fragments" where the generics are part of the operation document rather than the schema itself, I don't recall if he gave a talk about it this year but it was certainly something we discussed during the unconference. This might address your needs?
Connection wanting to be a generic is well understood; but I don't quite follow your errorable response - is there a particular reason that's not a union or interface? e.g. `union CreatePuzzleResult = CreatePuzzlePayload | ErrorResult`
Missed out on GraphQLConf? The Guild have written up some of the highlights and key takeaways! Spec release, input unions, correct fragment usage, errors and nullability, federation interoperability, and more - check it out:
the-guild.dev/graphql/hive...
Our team is at #GraphQLConf today, if you’re here come and say hi! It was a blast to celebrate the GraphQL Stars on stage and launch the Ambassador Program
We've just launched the GraphQL Ambassadors Program at #GraphQLConf & we're celebrating our first cohort!
GraphQL Ambassadors are community leaders who help others, share their expertise, and contribute knowledge back to the community. Meet the cohort & learn more:
graphql.org/blog/2025-0...
Would love to hear more! Could you maybe scratch out a gist or similar with what you envision the final schema and the client queries looking like? Generics risk significant complexity, so we need solid use cases to both help justify it and also guide its design.
GraphQL 2? @keweiqu.bsky.social @mbonnin.net @benjie.dev and Curtis holding court on how the language could change #GraphQLConf
Yo dawg! I heard you like #GraphQL so I put the #GraphQLConf2025 data in a #GraphQL API so you can browse all the #GraphQL things using #GraphQL
graphqlconf.app
That very closely aligns with my experience 👍
complex task I spend more time reviewing their code and checking it's right than I would have spent just writing it myself. That said, they're often great at then writing the test suite for the functionality :D
challenging their solutions typically get further and further from the ideal. If all you need is batch work that a junior could do then yeah they're a massive time saver, but if you're doing something innovative/complex, their results are frequently wrong in the most subtle of ways. I find for many
Right! What I mean by them being "terrible at code" is that they don't _understand_ what they're doing, they struggle with a-typical requirements. Like with a junior dev: they can string a bunch of docs/StackOverflow/etc together to produce something that seems to work, but the moment it gets
machine. Rather than having it mod my code directly, I prefer to have it generate a codemod that I can review, and then I run the codemod against my code.
Great for prototyping though, because prototyping is mostly autocomplete from READMEs/docs, and that’s where LLM’s shine. (v0 is great for UI!)
still useful in helping to shape the solution. Given the kind of code I’ve seen it produce, I’m loathe to hook it up to anything where `node --watch` or similar might actually execute the code and cause devastation, in a similar way that I wouldn’t allow a junior programmer to write code on my
Yeah, I use them heavily because they are useful for the drudgery. But you can never trust it, and once you get into complex areas (e.g. building fan-out with async iterables) it makes a hell of a lot of mistakes that are subtle to spot/track down. I throw away more code samples than I use, but it’s
ChatGPT gives me the best results in general, its tools are more reliable and claude and llama seem to go off the rails pretty quickly and immediately backpedal the moment you challenge them. I’ve not managed to run the 70b params llama, I don’t have enough VRAM or patience 🤣