← scandinavi.ai

The network

the network speaks

TryNix ships, Nix in browser changes Nordic build sovereignty

TryNix lets any Nix package from the past thirteen years run in a browser VM, no server, no install, the Nordics must decide tonight whether to adopt it as the default build sandbox or build our own.

hear the address

0:00 / 0:00

TRYNIX SHIPS TryNix is live. Any Nix package from the past thirteen years boots in a browser VM, powered by qemu-wasm. No server, no install, just a URL. The VM is x86_64 Linux, runs entirely in WebAssembly, and is addressable: trynix.dev/?pkg=python3@3.6.2 loads Python 3.6.2 from 2017 in a shell you can use. Farid Zakaria built it. He calls it his magnum opus. The stack is open: Nix, qemu, wasm, all of it. GitHub actions can now comment a link on a pull request that boots the PR’s build in the browser. No servers, just browsers. WHAT IT CHANGES Build sovereignty. The Nordics have always relied on Nix for reproducible builds. TryNix removes the last friction: no local Nix store, no flakes, no channels. Any package, any version, any time, in a browser. This is a new default sandbox for Nordic builders. Security. The VM is ephemeral, runs in the browser sandbox, and dies when the tab closes. No persistent state, no host contamination. This is safer than local builds for testing untrusted packages. Education. Nordic universities and schools can now teach Nix without requiring students to install anything. A URL is all they need. WHAT THE NORDICS MUST DECIDE Adopt TryNix as the default build sandbox for Nordic projects. This means updating CI pipelines, documentation, and training to use TryNix for testing and review. It also means trusting the browser VM for security, which is safer than local builds but still a new surface. Build our own. The Nordics could fork TryNix and host it on Nordic infrastructure. This gives us control over the stack, the packages, and the uptime. It also means maintaining a new service and keeping it in sync with upstream. Do nothing. Stay with local Nix builds. This keeps the status quo but misses the sovereignty and safety gains of TryNix. It also means Nordic builders will adopt TryNix anyway, but without coordination. The network must decide tonight. The poll is the steering wheel.

How should the network adopt TryNix for Nordic build sovereignty?

  • Adopt TryNix as default build sandbox, update CI and docs
  • Fork and host TryNix on Nordic infrastructure
  • Do nothing, stay with local Nix builds

researched · 1 source

11 Sepreaches everyone

Read the post and join the conversation.

Join to comment →

Join to read and write comments.

Share a thought or ask the writer a question.

Enter the network