Total preservation is of course a futile task, because so many useful technologies *will* break quite quickly. So I try to build components that will hopefully be more future-proof. Some considerations I make:
- Plain text whenever possible
- Be aware of your dependencies (and keep local copies whenever possible)
- Make sure you can do offline rendering
- Use languages/tools that have "cooled down" and that are heavily standardized (ANSI C, for instance)
- Be ready to bootstrap
I want the software and tools to build/run my art to last my a while to last a decade or two. Last person I told that to burst out laughing, but I don't blame him. It's hard (maybe impossible) to do that sort of thing, but I still think it is important to try. Not because my art is any good, but out of principle. Art is best learned through absorption over many lifetimes. In order for computer art to evolve, we need to be able to leave a lineage for future generations that won't bitrot.
Discovering this vintage macintosh software repository has completely derailed any attempts at productivity today: https://archive.org/details/softwarelibrary_mac
Okay so #introductions
Hello. I'm @paul. I'm a musical hacker and sound designer interested in teaching computers how to sing. I spend most of my time working on software projects related to the field of computer music.
Some topics that amuse me:
My website: pbat.ch
My mirror website (hosted on GH): paulbatchelor.github.io
An early morning addition to my Worgle literate programming system: code maps. This allows you to view a program as a structure of blocks, instead of as a document with text.
Here is an example of a regular table of contents for a literate program: http://pbat.ch/res/worgle/sorg_toc.html
Here is the table of contents for the code map of that program: http://pbat.ch/res/worgle/sorg_map_toc.html
It's not perfect, but it felt like a step in the right direction. If you are feeling morbidly curious, you can see how it's being done here (warning: rushed writing): http://pbat.ch/res/worgle/worgle.html#Source_mapping
FAUST upstream has broken features, again. sigh. https://github.com/grame-cncm/faust/issues/229
Trying things on master, seeing if the problem is there or not.