Skip to content

Dolly v0.1.4

Choose a tag to compare

@daugasauron daugasauron released this 30 Oct 23:01
· 2015 commits to main since this release

Dolly v0.1.4: 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.4/. Dolly is also on npm, to run in a page of your own.

New since v0.1.3

  • npm packages: @daugasauron/dolly, the runtime and its boot(element, options); one package per device host module, @daugasauron/dolly-host-NAME (display, input, gpu, audio, microphone, touch, upload, sockets, pty, and save for download@0); and two images, @daugasauron/dolly-image-default and @daugasauron/dolly-image-pi-minimal. The page chooses the image, its host modules, the HTTP policy and files written into the image before it starts. The README's "Pi with npm" runs Pi under a policy that admits one model provider, with three device host modules (display, input and download), and its server relays hosts that send no CORS headers. docs/agent-frontend.md is the guide for an agent in place of a web frontend: your instructions and skills as files beside the page, your backend's API, and the model's provider (a gateway, Bedrock's OpenAI-compatible endpoint, Copilot), with no image to rebuild. docs/embedding.md describes the packages.
  • The runtime runs in a Worker: the page exchanges messages with it and holds no view of kernel memory, and the Worker paints the display.
  • The seed's C/C++ compiler is the one the previous seed built inside Dolly.
  • exec: execve is part of the process contract; Slop's exec, env and command replace themselves with the program they name. cargo run works.
  • Go, with GOOS=dolly and GOARCH=wasm64: the go package builds Go programs inside Dolly, with go-sdk, go-build, go-tools and esbuild. net/http goes through Dolly's HTTP broker, os/signal receives the kernel's signals, and go get works.
  • OCaml 5.5 as a package, built inside Dolly from upstream's bootstrap compiler.
  • stack@0: recursion deeper than one browser stack, for programs rewritten by stack-wrap.
  • touch@0: the fingers on a touchscreen, each with its id. SDL2 and raylib programs receive them; fingers zooms and moves a figure with two.
  • The terminal reports the mouse to a program that asks (tmux's mouse and pane menu work) and draws CJK and emoji from fallback fonts. Emacs no longer runs out of stack at its first prompt in Chromium, and C-g interrupts it.
  • SDL2 plays sound through audio@0; sdl2-mixer, sdl2-ttf and sdl2-image are packages. Xonotic plays sound and draws on gpu@0, its shaders translated by naga, built inside Dolly.
  • 0 A.D.'s content is made inside Dolly (zero-ad-data).
  • Local models: Qwen3.5-4B at 3 bits and LFM2.5-2.6B, one package each.
  • janis-install installs npm packages from the registry, checked against their sha512 integrity; Pi is installed so, and pi-key reads a model key without showing it. vendor-crates vendors a Cargo project's crates.io crates.
  • Python has sqlite3, bz2 and lzma. Git clones, fetches and pushes local repositories. curl takes -d @FILE and --data-binary.
  • More packages: llvm (LLVM's tools, libraries and headers), llama-cpp, fmt, libxml2, libsodium, boost-headers, icu, premake, libogg, libvorbis, naga.
  • Processes: each is its own process group and session; up to 56 run at once, admitted under a memory budget, with 32 threads each. /proc lists processes and /dev/zero exists.

What stops working

  • buttons@0 is gone: touch@0 replaces it, and pi-phone's taps come from it.
  • The builder pages are gone, since the packages hold their own builds: /codex-build/, /llama-build/, /local-llm-build/, /mojo-build/, /mojo-runtime/, /neovim-build/, /openal-build/, /pi-build/, /speech-build/ and /xorg-server-build/.

Known gaps

  • In Chrome, a threaded program can stop with memory access out of bounds when it copies into or fills memory another thread has just grown: Chrome checks such accesses against the size it saw before the growth. It is rare and as old as threads; Firefox does not have it.
  • The npm packages hold two images and do not build images.
  • 0 A.D. in Firefox needs WebGPU on a display with hardware GL.
  • mojo run would need a JIT and refuses, saying to use mojo build. File modes and umask are not part of Dolly.
  • The Rust seed (stage 0), Dolly's kernel and its libc are still built outside Dolly.
  • GitHub Pages carries a subset of the catalog.

The domain version's file list (deployment.sha256) has SHA-256 1715778ce7e1a23a2eea8047ec214669476fb326d1b21a13bbe9fef4abc0f156.