Pascal Senn 🌶

@StatisticsFTW @cnakazawa yes - but thats a backend problem... graphql and its patterns make a lot of sense on the client, but i'd argue you get even more benefits when you have a graphql backend. especially when client and backend talk the same language..

@Pascal_Senn @cnakazawa TBF requiring a GraphQL backend is a pretty big lift. And plenty of people would prefer the lack of compilation step, as well.

fate 1.0: The first full Async React Metaframework New in 1.0: * Zero-Config Live Views via SSE * Drizzle Support * "Native" HTTP support (no tRPC) * Void Router * Vite plugin * Clientside Garbage Collection * Performance & scalability improvements fate.technology/posts/fate-1.0

@cnakazawa sure - i meant more that the concept of fragments and composition is part of the graphql query language and this is leveraged by relay, apollo client, urql etc.

@Pascal_Senn No. fate solves data management for the web. GraphQL is a transport protocol. Same as tRPC or any other JSON API. fate has a very simple protocol, it’s “just JavaScript”, http and batching.

@cnakazawa i see - already sending this through to folks that never got to experience relay so they can finally know what i am talking about 😅 so you'd say - fate partially solves a problem on a client that graphql solves higher up in the stack?

@Pascal_Senn People who get to experience it love Relay, but not everyone likes GraphQL. With fate, you get the best client framework without having to buy in to a backend query language.

@hrgooo @rickyfm hmm can you elaborate? isnt this pretty similar to a subscription and @appendNode and @deleteRecord ?

@Pascal_Senn @rickyfm One example: at large scale relay becomes challenging to update lists, this is solved here with live list views.

Finally someone did data fetching right

@cnakazawa So essentially: just because the backend does not provide a GraphQL interface? also, I've read through the docs and I like fate, dont get me wrong.

@Pascal_Senn Explained in the initial announcement: #a-modern-data-client-for-react" target="_blank" rel="nofollow noopener">fate.technology/posts/introduc…

Wrapping up another great API Days. Looking forward to seeing everyone next week at GraphQL Conf in California - registration is still open and free to attend. graphql.org/conf/2026/

GraphQL wasn’t made for AI. But it might be one of the best ways to talk to it. chillicream.com/blog/2026/04/2…

Clauding (verb) — Relentlessly hammering prompts into Claude with zero strategy and full confidence. You don’t understand the output. Claude doesn’t understand the input. But eventually, somehow, it works.​​​​​​​​​​​​​​​​ #Claude

Keynote Speaker: “AI is revolutionizing healthcare research and will help us defeat cancer. At scale. Very soon.” Meanwhile, Engineers (prompt to ChatGPT): “Give me 5 better names for the variable _aggregatedContextualConfigurationOverrideValue.”

🔥 Modern enterprises don’t have to be disconnected islands. See how agentic platforms turn silos into collaboration and intelligence at #GraphQL Day Paris graphql.day Catch the talk: From Isolated Services to Agentic Platforms - @michael_staib & @pascal_senn #AI

Congrats to @martinbonnin and @Pascal_Senn for being elected into the GraphQL TSC! graphql.org/blog/2025-02-0…

This week's #graphqlstar is the one and only @Pascal_Senn 🎉 Pascal has been an important contributor to the composite schema WG, website, and of course the spec! Thank you, Pascal!

@davidfowl @GKedzierski appsettings.json via swisslife-oss.github.io/Confix/

@GKedzierski How are you managing config?

The more I spend time in the devops space looking for what should be simple solutions to some problems I am appalled at the tooling state of the art. Absolutely developer hostile. It's clear why everyone tries to rebuild heroku.

I think it's beautiful that competitors in an ecosystem can come together to build a standard that is free for everyone to use and find common ground. The composite schema specification unifies all the best parts of existing federation solutions! 🌐✨

I really enjoyed working on the composite schema specification and am excited to push the boundaries of distributed GraphQL together with @theguilddev and @apollographql and all the others involved!

#GraphQLConf has come to an end, and what a fantastic conference it was! It was wonderful to finally meet in person all the amazing people I've been working with over the past year.

I have worked with numerous database systems over the years, but I don't think I've ever had a better experience than working with @ClickHouseDB. It feels like for every problem I have, there is a solution directly built into the database... such a joy to work with!

So,the next time you choose a technology for your projects,consider this:#GraphQL is not just about scalability, multi-modality, efficient data fetching et al. It unifies communication and makes your domain accessible to everyone. You dont have to be Facebook for it to make sense

Now, if a new requirement comes in, lets say, adding an address to the User. This is enough information for the backend dev to know where to add a field (extend the User type with the address field) and for the frontend dev to know where to expect the data, User.address.

In 1999 a NASA mission to Mars failed, because some engineers used imperial units while others used metric units. A good example of what happens when people do not talk about the same thing. This is also a common problem in software development.