lilypond: That gray area

I am very much on the fence when it comes to including lilypond on this list.

As I understand it, lilypond — the program — just converts text-based sheet music into a visual format (I believe the home page calls it “engraved”) not unlike what LaTeX does … although I know very little about that either.

So the net effect of lilypond is this:

2013-12-23-lv-r1fz6-lilypond

Text-based coding for sheet music converted into pdf format, without much of an interface or interaction.

That doesn’t discount it as a text-based application, any more than imagemagick or even inkscape, or some other tools that follow the same style.

That does drop it into a gray area though, where the benefit is in the output, and not the interface.

So is it a command-line application? Is it a true-blue text-only program?

I’m not going to fight through this one. I humbly submit that it does its job, interface or no interface, and if you need to draw some sort of line in the sand to reinforce an us-and-them mentality … then you’ve overlooked the real beauty of software like this — making life easier, and more beautiful.

Advertisements

10 thoughts on “lilypond: That gray area

  1. todixu

    I think it counts just as much as a roff or TeX implementation. After all, you can feed the output file to a printer control program without ever seeing it displayed on screen.

  2. Pingback: mencoder: mplayer’s less famous cousin | Inconsolation

  3. Pingback: privoxy: I feel obligated to mention it | Inconsolation

  4. Pingback: Fantasy I for Lute / Omer Katzir | The Silent Troubadour

  5. Pingback: groff: Typesetting, in any direction | Inconsolation

  6. Pingback: Markov notes: requirements, protocol and biblio | Cormul

  7. Pingback: darkstat: Making an exception again | Inconsolation

  8. Pingback: darkstat: Making an exception again | Linux Admins

  9. Pingback: Bonus: A dozen more remainders | Inconsolation

  10. Pingback: Bonus: A dozen more remainders | Linux Admins

Comments are closed.