FUN FACT (and i will continue posting facts and they will continue to be fun, until morale improves):
Building LibreWolf uses copious amounts of disk space. 1st terminal shows disk usage, updated every 2 secs; /home was using 0GB, now it's gigabytes (I'm building it in /home).
2nd terminal shows the build, in OpenBSD's ports system. 3rd shows CPU/RAM usage.
I'm re-testing building the latest LibreWolf on OpenBSD CURRENT. Hopefully my port will build!
(i'm ssh'd into openbsd on each terminal)
@moses_izumi i don't think running everything inside an interpreter is viable. lots of programs are performance-critical and a dynamic recompiler can only go so far. but your point is well-taken, thank you.
@moses_izumi like. you wouldn't write an emulator in python. that's strictly c/c++ or rust territory.
@fun still debian. my openbsd hostname is "shitbox". i do actual work on porting from my debian machine for the time being.
then i just push to a test branch and check out that branch on the openbsd machine, and build it.
so my debian machine is still my main machine, still hostname "unimatrix0". my openbsd dev machine, presently only used to test my librewolf builds, is a separate machine with the hostname "shitbox".
this is my openbsd box (my shitbox):
@fun and this is my debian desktop:
that text is actually a png file. i made the errors from earlier today (failed librewolf build) a wallpaper. the weird eye photo is captured from a specific frame in the movie Mad Max, just before the nightrider's car blows up with him in it.