Recent searches
Search options
Administered by:
So, I just decided to try out Inferno. Would be pretty straightforward to compile if they had a cleaner website without scattered and barely readable docs, weren't hosting on Bitbucket, using Git instead of Mercurial, if they made clearer that you need the whole multilib deps and putting the repo at the same path as mkconfig's $ROOT, and if they hadn't typed in a stupid bug that empties that variable.
well, I got limbo and emu binaries, I think this is it
also like
you know
YOU COULD TELL PEOPLE WHAT EMU IS AND HOW TO LAUNCH THE DESKTOP FROM IT
[UNMOVED] @espectalll@mstdn.ioanyway, Limbo is the definitive language and Inferno is going to beat the crap out of Java and WebAssembly, 2019 is the year of Inferno
I wish I found this before, but here's a proper guide to Inferno https://www.ueber.net/who/mjl/inferno/getting-started.html
Alright, just realized what was wrong.
Using Inferno with root: bad
Compiling Inferno with root and using it as an unprivileged user: bad
just casually decided to compile Inferno as a standalone OS
it no werkz
Well, I did a thing 
plan9port and Inferno versions of acme running on Musl Void via chroot
Notice, besides the obvious extra ugliness from Inferno's titlebar: one is "acme", the other is "inferno", one says /home/xerz, the other says /usr/xerz, one has that weird cursor with squares on its borders, the other one has a more simple straight line.
In more technical aspects, one is a native port while the other is running inside a Dis virtual machine on top of an emulator (some would say, a virtual machine inside a virtual machine?).