I've made some changes to wom. One of the largest one was getting rid of passing arguments when spawning a process. With arguments, we had two ways to pass data when starting a process: through the arguments or through files. I realized that we always want to use files. Without the program reading its state from its files, we have no way (simple) way to restore it when the OS is saved as a quine. A non-simple way I experimented with a bit was to save the arguments in a `prog` file, to be replayed on reboot. But then the argument file had to be kept in sync. And, if we have to use an argument file... we might as well just use files. So files always win.
I've updated the spawn syntax to allow passing initial data for files, which basically give keyword argument for free, without even needing arguments at all. So to spawn a directory at a path, we can just do `dir path=/foo/bar`.
All of this made me realize that processes are a lot like actors. They are responsible for their own work. But instead of exposing a single inbox, they expose files that the outside world can write to or read from.
I added a `ERR!` clickable label on the window when the process it runs has an error. Clicking on it will open the proc's err file. That file is never wiped. If you want to discard that error, you can erase it. Since wom is browser-based, the main goal of errors is to indicate that something failed. The browser's dev tool is the debugger you'd then want to use.
dir, the file browser program, will select the program to open based on the extension. Here's how it works: if you click on `myfile.foo`, dir will aim to find a `foo` program (in /bin) and will start it with a path file that will take the value of the file you just opened.
I changed other things as well, such as `bat`, the program runner. I'll talk about one another time!