This is well worth reading for any developer once you get past the first page or so. At first the complaints about existing software seem overblown because it's not obvious where the shortcomings are, but once you get into it it's an interesting study in how multiple small flaws can be seriously aggravating to the trained eye...and the dangers of unthinking abstraction that works fine in simple cases but falls apart when applied to more complex problems.
<i>Since typography relies on human judgement of appearance, people cannot be replaced. However, much of their dull work can be automated: if LilyPond solves most of the common situations correctly, then this will be a huge improvement over existing software. The remaining cases can be tuned by hand.</i><p>This is the thing that we so often forget: algorithms can take us a long way, but they can never completely replace judgement. Everybody should read this article, even if they couldn't care less about music notation. (I also particularly enjoyed the section on how not to design software.)
The care for detail here is overwhelming. Even if you care nothing at all about the content, it's a strong example of what can be achieved by striving for perfection.<p>I also find it interesting they turned to an algorithm similar to Knuth's TeX algorithm. "Minimizing ugliness" is a pretty potent computational metaphor for how detail oriented design work works, it seems.
I've been dying for the inverse of lilypond;an app that would allow you to take a picture and turn it into text notation/MIDI would be awesome.<p>That said, I used lilypond a couple of years ago and loved it.
I have only fired up lilypond a couple of times, but I have to say I am very impressed by this open source project. It obviously aims to be best in category.
One sentence that struck me was "Notation is an intricate symbolic diagramming language for visualizing an often much simpler musical concept."<p>Now if you remove the word "musical", it's true of notation in general. Any notation should reflect the structure of the thing it is notating; if music notation is typically more complex than the "often much simpler musical concept" then I would say musical notation is broken and should be changed.<p>Is musical notation broken? I've no idea, I don't know enough about it to say.
This reminded me very much of the great effort that Knuth (as a commenter mentioned) put into both his monumental TeX formatting system and MetaFont font generation program in a (imho) successful attempt to enable the preparation of beautiful math documents.<p>One thing that made TeX so successful is that it was designed to be open, and many packages (e.g., LaTeX) have been written to made it easier to use and more powerful. If LilyPond can be easily extended in the same way (i.e., programed in LilyPond, not C++), it might be similarly influential.
I find it interesting they refer to notes as quarter values or eighths. I can quickly see myself getting confused by that (is that a quaver? Did I do it right?) - does it change if you change the time signature from 4/4 to 3/4? (forgive the slashes)
Meh, I was writing out scores for a band; when I started using Finale the musicians thanked me profusely for making it readable.<p>Unless you can afford your own personal copyist, it's sort of irrelevant. The little formatting nits you learn to work around (or just talk the musicians through it with pencils, which you end up doing anyway for musical reasons)