WebVM
Why have we decided not to use the original WebVM?:
You may have noticed that clicking through to our Linux workspace redirects you to an external environment. We made this architectural choice to prioritize utility over novelty.
While purely client-side emulators (like WebVM) are remarkable technical achievements, they operate within the strict sandbox of your local browser cache (the specific WebAssembly Constraints are 32-bit memory addresses, locking you to 4 GB total content split into 2 blocks). This results in hard limitations: the inability to install significant software packages, restricted persistent storage, and an ephemeral nature that wipes your work the moment you refresh the page. For a student or professional attempting real-world tasks, these limitations often create more friction than productivity.
Why we chose OnWorks?:
- Beyond the 2GB Barrier: Unlike browser-contained emulators, the environment we have linked provides a dedicated ephemeral 30GB server-side workspace capacity required to install complex software stacks, development tools, and data-heavy applications that would otherwise crash a local WebVM. This dedicated virtual environment also comes with a dedicated 3GB RAM and 2 vCPUs (essentially 2 CPU cores) that you can access from any device with a web browser, and run practically any OS using it.
- Full Desktop GUI Integration: We believe a workspace should feel like a workstation. You aren’t confined to a text-only command line; you gain access to a full graphical desktop environment (GUI), allowing you to interact with your tools as you would on a physical computer.
- Seamless Workflow & Persistence: By utilizing a cloud-backed infrastructure, this environment offers better support for state management. With features like Google Drive session integration, your workspace becomes a tool you can actually return to, rather than a fully ephemeral experiment you have to rebuild from scratch.
- True Local-to-Remote Interoperability: Need to pull your results down to your local machine? Our chosen environment provides a robust bridge between the remote Linux instance and your local hardware, ensuring you can download your finished work easily without fighting browser-imposed file-system restrictions. OnWorks facilitates local downloads through a bridge built into their HTML5 VNC client. Because your browser is essentially acting as a window into their server, they have built a specific interface to handle the gap between the virtual desktop’s file system and your computer’s local storage.
Our goal is to help provide a tool for media and technical workflows. By leveraging this infrastructure, we are ensuring that when you land here to work you aren’t just testing a concept but gaining access to a functional, capable, and stable Linux desktop designed to keep up with your professional ambitions.