save states are something i've seen very few debugger-enabled interpreters have. on paper, it would probably be as easy as storing the state of the interpreter in a format like a core dump (only requires the ability of reflection)
fmixolydian
joined 1 month ago
cool!
i once tried to write a brainfuck jit compiler (that just appends raw bytes to a buffer and runs it as x86 machine code if it hits a branching instruction like [ / ])
understandable, given i picked up that language barely a week ago.
also, about rails crashing - it was bc rails wasn't importing ActiveSupport::LoggerThreadSafeLevel::Logger properly.
another reason i dont like rails is the sheer complexity of its project structure (seriously, 20 dirs/files for an empty project? django compared to that is like a feather to an anvil) - although some of its components (like active record) are admittedly fairly good, when used in isolation (if it wasn't for the fact that migrations don't work as rails is broken)
actually, in the production version i check if the sigsegv handler already got triggered at the start of the handler (to avoid a nested sigsegv) and just exit without any fancy error printing if that happened
i left it out of this meme bc it would've cluttered up the code snippet.