During my PhD, I went a bit out of my way to comment on the history of digital musical instruments. I felt that it could aid in motivating the reader for the myriad of more complex topics to come. The original section, with minor corrections, can be read at the link.
Recently, I have been getting into understanding synths and digital music production as they are at the intersection of my many hobbies (music, modeling, programming, electronics). It is a fascinating area, but also very demanding due to interdisciplinarity (and the gear is bloody expensive).
I wish I had the time and skill to read the whole 180 pages of your dissertation with full understanding, but I will spend some time with it. I like some of your diagrams already!
That is exactly what motivated me to pursue this theme: I like programming, a bit of math, music, and product development. Why not try to mix everything up? It was a nice ride and it made my PhD enjoyable. I am glad you found the thesis useful. I tried to make it as palatable as possible.
I've never used Quarto, but I might give it a go someday. I currently have a convoluted workflow for generating math-heavy documents that involves generating equations using SymPy in a notebook, accumulating them in a string, and ultimately dumping the string into a Markdown. I would love to simplify this sooner rather than later. I'm also keeping an eye on https://typst.app/ and hoping for a sane alternative to LaTeX to emerge.
In my experience with feeding large codebases to Gemini, simple tasks work ok (enumerate where such and such happens, find where a certain function is called, list TODOs throughout the code, etc), but tasks that require a bit more logic are trickier. Nevertheless, I had some success with moderate complex refactoring tasks in Python codebases.
I can think of no use case where binaries are desired in such representation, so I might bake binary exclusion into CodeWeaver as well. SVGs, on the other hand, might be wanted sometimes, in web design contexts. I'll take a look at your implementation and see what I can learn.
Some advantages of CodeWeaver are that it is compiled, so it might be faster; you can grab a compatible executable from the releases section instead of using `go install` so, no dependencies. You can manually specify what to exclude via a comma-separated list of regular expressions so it might be more flexible. I never used Repomix so, those assumptions might not hold. On the other hand, remix seems to be awfully more complete, a full-fledged solution to convert source code to monolithic representations. I wrote CodeWeaver because I only needed something that worked and, occasionally, I could trust to keep sensitive data away from sketchy LLMs (And wasn't aware of other solutions).