@neauoire i always seem to wind up doing an infinite rule 30/rule 110 scroll for my demos

@neauoire idk i think people love mandelbrot

@neauoire Sorry, but what's that in American?

[sorry. I know I'm not funny.]

@neauoire feels weird to fave this because I hate what it’s saying but it’s also a very good way to say it.

@neauoire we are all gonna die 👀

I rarely use borders and frames in my interfaces, but I wanted to try something different.

@neauoire OH THATS SICKK are these regular symbols in the .sym file??

@neauoire Do you think it would be possible to add proper breakpoints? Not just BRK, but: go until here and then let me step through from there?

@neauoire Are you sure this isn't caused by a currency conversion? That sounds like about one dollar usd converted to Canadian

@neauoire it would be better if they did 937417

@neauoire VAT here forces 1 to 1.21 :)

@neauoire some of these tapes were doing that in the 80s and i never knew why. a retensioning procedure was recommended but didn't seem to help.

@neauoire @cstross Oof. Reading TFA just brings sweat to my brow and shaking to my hands.

@neauoire I still have a drive from a SInclair computer, an endless reel of tape in a small case

@neauoire https://www.olivettiani.org/the-mysterious-affair-at-olivetti.html

@neauoire do not open old wounds... :flan_piteous:

@neauoire All that binary editing stuff was super interesting, but this is wonderful as well! I've already taken it for a spin and love it.

@neauoire this is amazeballs

@neauoire this was the original post: https://merveilles.town/@nasser/109265538480410221

I was thinking about programming specifically, particularly dynamic and static types at the time

@neauoire :: So it's like a fallthrough for subroutines?

@neauoire this is why im making my own version control system

@neauoire oh, to be building every day......

I made an arity checker(it's a thing that makes sure that a program's function doesn't leave the stack in an unexpected state), and would run it over my assembler source and it threw an error at my error handling code. Each time I thought, it's probably being confused.

But NO, it was telling me this whole time what I should change . I gave it a second look today and fixing that little thing was all I needed this whole time to get it to work properly. Thank you arity checker sensei.

@neauoire feels like this'd have parsing benefits - could likely parse something faster if you already have the binary representation, could be as simple as copying into memory

@neauoire yes! this is how co works, the source code is natively a bytecode, and there is even a subset of the instruction set reserved specifically for source-only tokens (like newlines, indents, comments, and different types of label definitions) and then the text representation is really just a transformation layer/interface. and then there is also a symbol database integrated to the language tooling, similar to the “symbol file” you mentioned (i imagine?)

So a few days I've realized that I very much liked working using structured editing.

Structured editing means that your editor is aware of the program's functioning enough that it handles how it should be presented, so you're not editing text as much as the underlying structure of the program.

It's just a fancy way of saying that it's basically just a symbols aware disassembler.

I've spent the past 2 days improving the UX so I could run the reassembler without going through the terminal.

@neauoire are the labels and comments stored in the sym file?

@neauoire kickass 💪 and then the images too 😉

@neauoire Off-topic, but that Cream font you customized looks glorious every time I see it in one of your posts. I’m curious if there’s any existing way to convert the UFX font to something like OTF?

@neauoire Every time I just want to loosen my ligaments, some stretchypant shaman is trying to make me think of the cosmos. What a weird sense of humour they must have.

@neauoire @spiralganglion Ooh, I have a counter-example: getting eaten (most often)

@neauoire love this, it's going to be really helpful. ooh, and thank you for making labels no longer overshadow the byte they're on top of, I think that's a fantastic change :)