Comment by oliverpaddock
2 months ago
A few months ago I outlined a spec for a new modern programming language inspired by LilyPond I call Capo. I haven’t done anything with it yet but the idea is that it compiles to MNX, which is the (still in development) successor to MusicXML, becoming a language that could be used as a scripting language in any program that supports MNX or as a standalone text-based music tool. Thought this group might find it interesting: https://github.com/Capo-Lang/capo
Can you give a rundown on how it differs from lilypond? What deficiencies you are addressing?
It’s mostly just for fun, but lilypond has a bit of outdated syntax in modern programming terms. The main difference though is that lilypond compiles to music engraving, whereas capo compiles to a more universal file format that can then be used to engrave, or inserted into another file, or opened in another program.