It is like a UX report, and the author has every right to make one! But I'm afraid that if this were a pull request into the western-music-notation repository t

It is like a UX report, and the author has every right to make one! But I'm afraid that if this were a pull request into the western-music-notation repository then I would find it hard to resist closing it quickly. Yes, it is true that using a piece of software shouldn't require a CS degree. But you still expect the source code to follow "CS principles". Similarly, you expect scores to follow "music theory principles". Now, it takes time and effort to understand these principles, just like with CS. However, whereas almost everybody understands that the subject of computer science is vast and is not to be underestimated, the same doesn't seem to be the case for music theory. And I can sort of understand why - computer science is math (1 + 1 = 2), but music theory is just hand-wavy rules made up by dead people, no? Well, yes, but that does not make it any less "true". Music theory as a tradition is very real, and you can't expect people to take your music-theory "PEPs" seriously unless you have been deeply embedded in that tradition. Of course, this is not me knocking the author in any way. Sometimes the best innovations come to those with fresh eyes. But I just hope to convey the idea that music theory (or maybe more accurate to say "music tradition") is not something to be easily dismissed and, just like in computer science, a good solution requires a good understanding of the problem.