Repository navigation
Dolly v0.1.6
Dolly v0.1.6: a modular POSIX-like userspace in a browser tab, built from source inside the tab from a C/C++ compiler seed.
This version is https://slopshare.dev/v0.1.6/.
The site now serves v0.1.4, v0.1.5 and v0.1.6: Cloudflare Pages holds 20,000 files a deployment, and v0.1.0 to v0.1.3 are no longer online. Their tags and releases here remain.
New since v0.1.5
- npm: a sandboxed Pi agent of your own, from
npm install @daugasauron/dolly-buildalone.npx dolly-build init my-pi git python nviminstalls what it names and writes the project: Pi with those tools, an HTTP policy that admits the model's provider alone, skills as directories underpublic/skills/, and a GitHub Actions workflow.dolly-build addadds tools later. From an empty directory,inittook 2 s and the build 45 s, for a 94 MB site. In the test, the flow and a CI build from a fresh clone ran in Chromium and Firefox with only loopback reachable. Pi there has anuploadtool: it asks the user for a file through the page's dialog and gets its path, or that the user cancelled. Every module's header and client is a package on npm too (libdolly-displayand twelve more), for a recipe that compiles against one. The guide isdocs/npm.md, the changelogdocs/npm-changelog.md, anddocs/npm-upgrading.mdtakes a 0.1.5 project orboot()page to 0.1.6: a 0.1.5 project from npm, upgraded by its steps, showed Pi's screen 3.4 s after a first visit in Chrome and 4.2 s in Firefox, against 6.9 and 14.6 s on 0.1.5. - Sessions: a save is the whole filesystem, up to 8 GiB, and a restore boots from it without downloading the image, Pi's conversations included. The site's runtime (3.5 MB) is kept with it, so a saved session opens with the server stopped, in Chrome and Firefox. A saved tab asks before it is left with unsaved changes. Files over 2 GiB save, restore and recover. 300,000 files saved in 3.3 s and restored in 1.8 s.
- Godot 4.7.2, built inside Dolly by SCons, with its editor and a driver on
gpu@0: SPIRV-Tools and Tint, also built inside Dolly, translate its shaders to WGSL for the Mobile and Forward+ renderers. Its hardware test ran at 56 to 60 frames a second in Chrome and 59 in Firefox, and in Chrome the editor shows its 2D or 3D view 128 or 80 ms after a click, where Mesa's software renderer took about 0.7 and 1.6 s. Games: Lantern Drift, Airtime, Truck Town, Dodge the Creeps and Voxel Flyover, an endless world drawn by shaders with a corgi on a jet surfboard: its trees are drawn in four rings of detail that cross-fade, so nothing pops, and it ran at 60 frames a second in Chrome and 59 in Firefox on the test machine's RTX 5070. - Xonotic draws its walls on
gpu@0: vertex-lit and lightmapped surfaces had no WGSL and were skipped, and the ultra preset drew black. Boil now draws solid walls in Chrome and Firefox, and a six-bot match at the high preset ran at 60 frames a second at 1280 by 720 in Chrome. - X11: in
x11-desktop,amy install godot-editor lantern-driftoramy install photocraft, then the command, opens a window under twm; Lantern Drift's showed 28.2 frames a second in Chrome and 49.0 in Firefox. PhotoCraft, an image editor in Rust, is built inside Dolly.clipboard@0copies and pastes between the browser and Godot's editor or PhotoCraft, and writes the browser's clipboard only with the user's activation. Ctrl+C no longer ends the X session, and a key's echo in Neovim under Ghostty takes 0.15 s, not 1.2 s. - rclone 1.76.0, built inside Dolly by the Go toolchain: after
amy install rclone,rclone bisynckeeps a session folder in step with one the machine serves withrclone serve webdav, through the page's HTTP broker. A bisync without changes took about 0.1 s, and a 16 MiB upload 0.5 s in Chrome. console@0: a host holds a terminal into a session with a program on it, or three pipes with standard error apart. A page opens one withopenConsole(); a native host on wasmtime runs sessions through the same contract.- Host modules: the kernel, supervisor and process Worker name none of them, and most modules ship their headers and client in a package of their own. With console, pty, dso, stack and sockets removed from
host/manifests.mjs, the runtime built anddefaultbooted. The kernel, not the host, decides signals' grace, deadlines and Ctrl-C's targets. - ABI contracts as data:
dist/dolly-abi.jsonholds each contract's constants and digest, the errno numbers and each process packet's layout; snapshot and image-entry limits are constants ofabi/dolly-image-0.wat. A second host on wasmtime reads them from there, and the 13 images it built matched the release candidate's byte for byte. - The seed's compiler (Clang and LLD of LLVM 24) names no host module: what
-pthreadand-rdynamicexport comes from the modules' manifests.cc -sstrips and-ftemplate-depth=Nworks. Built inside Dolly by the seed that holds it, the compiler is the pinned one again, byte for byte, and a second checkout with no caches builds the same runtime and image inputs. - Startup: a page fetches the packs it will read ahead of the one it reads and checks only its own image's metadata; a warm reload of
pi-agentwent from 2.05 to 0.9 s, and its first visit from 10.4 to 4.7 s. src/is nowkernel/,process/,page/,site/andprograms/. A page imports./dolly/page/browser.mjs, not./dolly/src/browser.mjs; a 0.1.5 project changes that, installsdolly-buildat 0.1.6 and runsnpx dolly-build add NAME.- The demos page (https://slopshare.dev/v0.1.6/agents/) has 44 recordings. New: Truck Town; Airtime changed in Godot's editor; TinyCC on Wine's desktop; an X11 workbench; the rclone folder; Voxel Flyover; Pi on a local model; a session from Chrome to Firefox; and the npm flow with Pi using a project's skill.
Known limits
- The workflow
initwrites has not run on GitHub's runners, andinit's install is measured with npm alone. - Firefox has neither of WebGPU's texture format tiers: Godot's SSIL, VoxelGI, SDFGI and depth of field do nothing there.
- Xonotic draws no shadow maps at ultra and above.
- From the public site, rclone reaches the machine's server only after the browser's local network access prompt.
- Offline, a saved session loads; the menu and image routes do not.
- The GPU contract tests ran in Chrome alone: the installed Firefox snap does not start in a systemd unit on the test machine.