Live data from Hacker News

Show HN: Syncular – offline-first SQL sync with TypeScript and Rust cores

github.com

41–44 of 44 posts

Re: Show HN: Syncular – offline-first SQL sync with TypeScript and Rust cores

#41

The README phrasing has vibecoding tells right away

The README has had plenty of LLM help, yes. I’ve described how I use them here: https://syncular.dev/llms/

I’ll keep refining it (talking about docs, tests, benchmarks etc). LLMs are involved throughout Syncular, as they are in my other projects, but this sure wasn't prompted into existence, its been built on and off over a lot of time. Have spent years deep in the offline-first rabbit hole. Most code, design and its trade-offs come from that experience and predate LLMs.

Re: Show HN: Syncular – offline-first SQL sync with TypeScript and Rust cores

#42
post #11
post #9

In which way this is different from PowerSync?

Both use local SQLite and keep the backend authoritative. The main difference is that PowerSync mostly handles downstream replication and gives you an upload queue; your API still owns the write semantics. Syncular specifies the whole round trip. Durable commits, auth scopes, conflicts, replay, revocation and bootstrap. Syncular also goes further up the stack: schemas plus SQL/SYQL generate typed queries for TS, Swif…

Hey PowerSyncer here :)

Firstly, it's awesome that you are using @sqlite.org/sqlite-wasm for your client-side SQLite database. We really like wa-sqlite ourselves.

We're currently implementing this proposal https://github.com/orgs/powersync-ja/discussions/376, which will speedup the sync throughput a lot - this was a natural next step for us as we have users with massive datasets (syncing a million plus rows).

Sidebar: What has your experience with OPFS+SQLite been like on sqlite-wasm? We have seen our fair share of issues on Safari/web kit.

Re: Show HN: Syncular – offline-first SQL sync with TypeScript and Rust cores

#43
post #11

Earlier quoted context omitted.

Both use local SQLite and keep the backend authoritative. The main difference is that PowerSync mostly handles downstream replication and gives you an upload queue; your API still owns the write semantics. Syncular specifies the whole round trip. Durable commits, auth scopes, conflicts, replay, revocation and bootstrap. Syncular also goes further up the stack: schemas plus SQL/SYQL generate typed queries for TS, Swif…

Hey PowerSyncer here :) Firstly, it's awesome that you are using @sqlite.org/sqlite-wasm for your client-side SQLite database. We really like wa-sqlite ourselves. We're currently implementing this proposal https://github.com/orgs/powersync-ja/discussions/376 , which will speedup the sync throughput a lot - this was a natural next step for us as we have users with massive datasets (syncing a million plus rows). Sideba…

Hey, nice, looks like I’ll have to rerun the benchmarks soon!

sqlite-wasm with opfs-sahpool has mostly behaved. No OPFS in private mode, storage may be evicted, handles can’t be passed to workers, and webviews may close them when backgrounded.

We open SQLite inside one dedicated worker and proxy other tabs through it, so that avoids some of the mess. Tauri uses native SQLite.

Re: Show HN: Syncular – offline-first SQL sync with TypeScript and Rust cores

#44

I wish there was an established way to build local first software with a robust syncing in the background, either P2P or to a server. I feel projects like this for local first and projects like Iroh for connectivity over NAT and through firewalls need to come together more. It would be could to have a drop in framework for this.

[dead]
Post reply on HN