making my own browser framework that can use something like librewolf as a web renderer and other graphical components and runtimes for other protocols. though I think that means that i’ll be retiring tomo-el-fuego in favor of a different runtime architecture. there’s a lot that I like about inferno, but modernizing it enough to actually use anywhere is another story. I doubt this is the end of my infernal experiments, but I can only do so much at a time innit.

Y se tomó la Coca-Cola del olvido, la realidad de muchos cuando se van del país.

Y se tomó la Coca-Cola del olvido, la realidad de muchos cuando se van del país.

in some ways, tomo el fuego is an effort to break away from electron and javascript as the basis for application development. specifically p2p messaging, but there are a lot of general applications too. its true that i could have set this concern aside to focus on making the p2p things that i’ve been talking about over the last several years. i might have done something there, but i really don’t want to accept the status quo there. i want a much smaller foundation to build on than a web browser and an event library with V8 bolted on. dynamic 9-flavored p2p is coming, but there’s quite a bit more foundational work to do first.

one way or another, tomo el fuego is slowly coming together #osdev https://sunshinegardens.org/~xj9/wiki/tomo/

dev snapshots of tomo el fuego are now available https://sunshinegardens.org/~xj9/wiki/tomo/ #tomo #inferno #plan9

inferno is not GPL anymore and i’m so happy. insta merge that shit boii https://src.sunshinegardens.org/~xj9/tomo/graph

tomo is updated and NO LONGER GPL gemini://sunshinegardens.org/~xj9/posts/2021-05-05-tomo-inferno-license/

tomo - a stripped-down inferno distribution and FORTH runtime for building graphical network applications