@dougmerritt is this difference unimportant because I'm running it single threaded, so everything is automatically time-ordered? What change happens that will make VHDL's spec of signals and processes matter?
@dougmerritt a while ago, I think you asked me whether it was important to have an action queue with both push and append, like I made. I found so far that while I originally only-used-append, now I'm basically only-using-push (and generally resolving as fast as being pushed). I originally modelled this on VHDL, which has two useful notions of time passing: ~ signals, but also processes. It's not defined what "happens first" on a signal. But processes force an order in infinitesimal deltas.
@synlogic I use an inclusive definition of emacs that basically includes the 60s, so I was shocked to discover recently that by my own standards, vi is an emacs (ie it was a modeful screen editor developed with explicit reference to and in the emacs compatibility space) @flyingsaceur
@mdhughes I'm just throwing in subgraphs of rooms and connections people loosely want as a starting point, if you feel enthused later we could do a git submodule @theruran@gnemmi@vidak
@theruran Okay, I just drafted you in here; adjustments and additions l m k, graphviz dot's clustering algorithms take up with bell labs primarily. (uiop:ensure-package :theruran)
{ @create $room :named theruran::comfy-forest } x ..theruran::reading-nook } x ..theruran::memsafe-workshop } x
@gnemmi I think that sharing our completely-real-computer-programs-and-writing by creating them as tangible, shareable objects in a sort of medley of "roleplay" laboratories and places gives us opportunities for real collaboration that are a bit harder if I just say, well, you could download my git and familiarize yourself with the code... So, thank-you for helping get us started! @vidak
@gnemmi Thank-you for joining in first! You can always let me know if you have new ideas for rooms and connections, or would like to add some writing to a room or something. (We can talk about actually-joining-in the world as it grows later). @vidak
@vidak Yeah the DSL would work great for that (maybe not the whole common lisp image thing..). I've been shy about taking a run at implementing @dump - which I will do in a way that can be loaded either into either of lispmoo2 or lambdamoo (but I will need to lay some groundwork inside lambdamoo for this to work without hitch, and the consuming-of-common-lisp will be verboten for those purposes, like your 8 bit port idea) @dig@gnemmi