Here be dragons

This section shares information on Metawork's roadmap and yet-unsupported use cases.

Multi-player mode

Using Metawork to collaborate with others is powerful. We're not introducing this feature during the Metawork alpha due to the operational complexity. However, we use multi-player mode internally and welcome interested users who want to collaborate with others via Metawork to contact us to try it out.

Reach out to @dmr by DM on our Discord server for assistance.

Production and CI environments

During the Metawork alpha, we don't encourage use of Metawork in sensitive production systems.

Similar to other cutting-edge features, we don't practice what we preach here in our docs—we do use Metawork in production internally.

If you absolutely must try out Metawork in a CI or production environment, reach out to @dmr by DM on our Discord server for assistance.

Windows Subsystem for Linux (WSL)

Metawork currently supports Linux and MacOS. During the alpha, some users have requested access to Metawork on Windows Subsystem for Linux (WSL)

While this isn’t an actively-supported environment, we have run Metawork on WSL using the following steps:

1. Ensure you are running WSL2 (there is currently no documented path to running Metawork on WSL1)

  • When upgrading Debian install from WSL1 to WSL2 it sometimes appears to hang for reasons unrelated to Metawork. If this happens to you, try installing WSL2 straight from the appx bundle.

2. Run apt upgrade or apt install curl

3. Install the Metawork CLI

eval "$(curl -fsSL get.metawork.com)"

4. Delete a WSL2-incompatible file

rm ~/.metawork/crashpad_handler

5. Install Metawork-flavored language runtime

mw install ruby
mw install node

6. Run a tutorial script

ruby "$METAWORK_HOME/learn/ruby.rb"
node "$METAWORK_HOME/learn/node.js"

While we’re not planning on supporting WSL actively in the near future, we appreciate users’ feedback and will help find workarounds for issues encountered with WSL.