News for hackers. Stuff that matters.

quambo

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.

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.

That’s kinda the tension I wanted to avoid. I’m not trying to make the whole SQL database a CRDT.

CRDTs are opt-in per column. A row can keep normal, queryable fields like project_id, status, and title, while one doc column stores Yjs/yrs bytes. Concurrent edits to that column are merged by the server; normal columns still use versions and explicit conflicts. Flutter uses yrs through the shared Rust core.

The trade-off is that SQL can’t query inside the CRDT document. Anything you need for filtering, joins, or aggregates should remain an ordinary column. That boundary gives you relational queries without giving up CRDTs where they’re really useful.

I’d be interested in your feedback on the Flutter client. I chose a very small C ABI—five hand-written dart:ffi bindings into the Rust core, rather than generating a large FFI surface. The app-specific schema, row types, subscriptions, and typed SQL/SYQL queries are generated from the shared schema IR using syncular generate. I’d love to hear how that feels compared with your flutter_rust_bridge setup.

More detail: https://syncular.dev/concepts-crdt/ https://syncular.dev/platform-flutter/

Thanks for pointing me there! Posted to their discord, but seems not so active.
Nice! Would recommend to decouple as much as possible and have tons of testing, every issue thats catched before having to go to the length of debugging client side issues is gonna save some sleep. Have been there, learned the hard way..

Whats your app?

It’s great to see apps being shipped with offline first (and flawless syncing as an optional feature) from ground up, sad to see many modern notes apps like notion or capacities treating offline as afterthought. But alas, it’s still a non trivial nut to crack.

Hope one day offline first will be a default and a solved problem.

Hi HN! I’ve been circling this problem for a long time.

In 2019 I built an offline-first datastore called debe. It used CRDTs and multi-master replication and never became something I could confidently ship. It did teach me that convergence is only a small part of sync. The difficult parts are durable writes, authorization changes, lost acknowledgements, schema upgrades, bounded bootstrap, and explaining what happened after something fails.

I eventually came back to the problem and built Syncular over the last year.

Every client has a real SQLite database: sqlite-wasm on OPFS in the browser and native SQLite elsewhere. Writes apply locally and enter a durable outbox in the same transaction. A server-authoritative commit log validates and orders them, using explicit scopes resolved inside the application backend.

The protocol is written down independently of the implementations. SSP2 is currently a draft, with canonical binary encoding and golden byte vectors. There are independent TypeScript and Rust client cores, both run against the same 95-scenario conformance catalog. The Rust core is exposed through Swift, Kotlin, Flutter, React Native, Tauri, Rust, and a small C API.

It also includes realtime WebSocket sync, resumable bootstrap segments, explicit conflict evidence, authorization revocation and local purge, windowed replicas, blobs, optional CRDT columns, per-column encryption, and typesafe generated queries for five languages. Important boundaries: it is pre-1.0, self-hosted, and there is no managed service or peer-to-peer mode. Native packaging maturity still varies by ecosystem.

Let me know what you think, I'm happy about feedback!

Demo: https://demo.syncular.dev Protocol: https://github.com/syncular/syncular/blob/main/docs/SPEC.md Background: https://syncular.dev/blog/offline-first-writes/ Docs: https://syncular.dev/

Re:Play.js: The Node.js and React Native IDE for iPhone and iPad on Saturday February 23, 2019 @06:30AM (#19232802)
I've just found a solution that works pretty nicely for me: Coda. It has an integrated SSH terminal, it has FTPS and uploads changes to files on save and it has support for many languages (don't know about rust though). It also saves your terminals and open files within each project so you can easily switch around.

Coda on iPad + Raspberry Pi (or an old Mac mini) make a pretty nice dev environment.

If you are more of a VIM guy, something like Terminus works well too.