avocado goblin @a_breakin_glass@cybre.space

@papush oh no

@natecull @enkiv2 eliminating the runtime/compile time distinction would help solve the problem

@natecull @enkiv2 surely this is a backwards way of looking at the problem

,

@feld @SlicerDicer @impiaaa NN used a supported toolkit afaik

@ben @DissidentKitty @FuchsiaShock scorching take

@Sapphicgiraffic cracking DRM with a corpse

@spottyfox sounds good tbh

@Dee why would you need that

@Dee wut

Common Lisp but with syntax-case macros

@papush you're being (pa)pushed out?

@thamesynne a CP/M macro processor? huh

@grainloom yeah

@grainloom fully concatenative shells when

@grainloom haskell vs m4

@RobinHood mandate from hiking

@trickster since m4 is turning complete, I suppose you could use it to store variables to later be freed

@trickster m4 macros for memory management