Rust Powers Shared Editing Across Web, Desktop & Mobile

ملخص

Pixel shares a look at how Rust code powers real-time collaboration and resilient document editing across Tunc Doc in the browser and Tunc Hub on desktop and mobile. The announcement highlights WebAssembly, anchored-change rebasing, explicit conflict reporting, and the importance of handling stale state and large agent edits carefully.

DEV Community

Rust: My secret weapon for code reuse in desktops, mobile, and web

My own independent alternative to Google Docs reuses Tunc WebSocket communications to deliver co-editing features in native Hub and the browser. Tunc Rust code rebases anchored changes and reports explicit conflicts. The same editing rules support people and agents contributing to a draft. WebAssembly runs shared Rust logic in the browser, with adapters for its APIs. It means that much of the Tunc codebase is shared between web-based Tunc Doc document editing and Tunc Hub desktop and mobile applications. That shared code covers real-time communications and data resilience; the same code runs in the web browser as WebAssembly, and also powers desktop and mobile on all platforms. All thanks to Rust. We still have to handle stale state and conflicts carefully. Large agent changes can take an atomic storage path and appear after the next save or reopening, rather than arriving live. Explore the service during the soft opening: https://tuncdoc.com/ The language and library maintainers make this reuse practical. Their work deserves credit alongside the service built on it.
Rust Powers Shared Editing Across Web, Desktop & Mobile
Powered by Readybot.io

الأحدث من Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …