JSLinux Now Supports x86_64

Original Article ↗ Hacker News Discussion ↗

Use cases and applications

  • Used for teaching Linux shell and development in classrooms that only have Windows PCs; also for technical interviews.
  • Convenient for quick experiments with compilers or “weird” code, without installing local toolchains or spinning up full VMs.
  • Acts as a zero-install build environment or C/C++ teaching platform delivered via a browser.
  • Enables web-based demos of hobby OSes or legacy applications that would otherwise be hard to run, and could underpin browser-accessible software archives.
  • Some envision it as a “digital sand mandala”: an impressive technical art project whose value is exploratory rather than strictly practical.

Networking and sandboxing

  • The VM has internet access via a websocket VPN with bandwidth and connection limits; users note you can run tools like ssh and nmap, raising questions about abuse and port 25 access.
  • Seen as a cheap, contained environment for testing networked software.
  • Discussed as a potential sandbox for “agentic” workloads, with debate over whether niche emulators are safer than hardened VMs. Critics argue obscurity is a weak and shrinking security moat.

Open source status and alternatives

  • The x86_64 emulation source and build config are not provided; some find this disappointing and suggest it should be clearly documented.
  • Alternatives mentioned include v86 (fully open but currently 32‑bit only), container2wasm (x86_64 via Bochs fork, but more limited UI), linux-wasm, WebVM, BrowserPod, Apptron, and web-based devcontainer setups.

Performance and architecture

  • Benchmarks show RISC‑V guests running significantly faster than x86 and x86_64 in this environment; participants attribute this mainly to easier emulation, though some question how general that conclusion is and note differing GCC versions.
  • Browser-based x86 emulation is widely acknowledged as much slower than native (tens of times or worse for some workloads), but still considered impressively usable for moderate tasks.

AI/agents and browser Linux

  • A substantial subthread discusses running coding agents against a full Linux environment inside the browser via WASM.
  • Proponents argue Bash plus a filesystem is the single most powerful “tool” for LLM-based agents; they prefer bundling a small Linux/WASM image over reimplementing Unix tools in JavaScript/TypeScript.
  • Others call this overengineered and inefficient, suggesting local containers or cloud VMs are simpler and faster, and expressing broader fatigue or skepticism about LLM-centric use cases.

Miscellaneous

  • Some celebrate the availability of classic systems (e.g., Windows 2000) and lament modern UI design.
  • TempleOS was successfully ported to the x86_64 JSLinux backend.
  • There is curiosity about whether JSLinux uses pure interpretation or JIT, and speculation about extending similar techniques to other systems (e.g., Android).