Conversation
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
robacourt
force-pushed
the
rob/subqueries-blog
branch
2 times, most recently
from
a37d49a to
5fe0fcb
Compare
|
|
||
| Sync is what makes apps feel instant. The data is already there when a screen renders. Another user changes something and your UI stays current. You can refresh, reconnect, switch devices, and keep going. | ||
|
|
||
| That is the broad pitch. We have written more about how [sync replaces data fetching](/blog/2025/04/22/untangling-llm-spaghetti) and why it is the right foundation for [collaborative, real-time apps](/blog/2025/04/09/building-ai-apps-on-sync). |
There was a problem hiding this comment.
They're both AI links but we don't mention AI in the blog. Maybe that's fine 🤷♂️
robacourt
force-pushed
the
rob/subqueries-blog
branch
from
ebe7f59 to
1d2293c
Compare
|
Reads great. Short and to the point. One qualm I have is that it ends a bit abruptly. I would try ending the post on a positivie note that highlights what other use cases get unlocked with this change. Like some examples that were present in the original draft of the post could be useful for people to grok the unlocked use cases and avoid getting boxed in by the specific document syncing example that is threaded through the latest draft. |
|
I'm surprised to see this post in this form. We obviously started with #4076 No problem to simplify the scope of the "deep dive" but I would have liked to be looped in on that. On the post itself, the lead in doesn't make sense; we're talking about sub-queries as if people know what they are. Compare the lead in of: a) https://deploy-preview-4076--electric-next.netlify.app/blog/2026/03/31/subqueries-deep-dive It's night and day. |
4 participants
Subqueries blog:
https://deploy-preview-4138--electric-next.netlify.app/blog/2026/04/27/subqueries
Also includes a documentation update