@GergelyOrosz Agents working in gh PRs should be an antipattern, only human relevant info should be elevated to humans. Your agent harness should reconcile all issues before bothering humans with their slop -> this must run in codegen loop
@yagiznizipli@Cloudflare Give us a sync engine with permissions, TS client library, and events that trigger a worker!
I want @linear style sync built into workers/D1. Then I can live the rest of my life happily in cloudflare land! Every web app needs it
SaaS companies should refrain from charging for unused licenses. Imagine the long-term trust built by letting customers know you reduced their bill compared to squeezing out some extra during some months!
@theo We're far from consensus on what "local-first" and "sync engines" are. I'd argue that moving data between server and clients should be easier for developers, sync engines might be part of the solution for certain apps!
https://t.co/5ynjjkHtny
@chrisseltzer On the other hand, my highly personal opinion is that many web apps are simple and when they get complicated, you almost always have to redesign them anyway ๐ค
@chrisseltzer Thanks for expanding on it! I think you raise some very valid points. The complexity of the interface for configuring the sync engine might over time introduce more problems than it solves. Especially with regards to easily introducing bugs that might expose PII and other data.