Wow, thanks for the feedback and compliments to my software. I will try to cover as many things as I can:
1. It's a domain specific language. If you compare syntax in Unison and LilyPond, you will notice that in Unison I tried to avoid all cryptic characters, symbols and terms that potentially can be misunderstood. All the keys words in Unison are accepted musical terms. The idea was that if you get the text written in Unison DSL, then just by looking at it, you can easily reproduce the music score with pen and paper (or digitally).
2. So, there are indeed two types of music score editors: WYSIWYG(What You See is What You Get) and WYSIWYM(What You See is What You Mean). If you prefer first type, it's okay. In ideal world they should work perfectly, but let's be honest - most (maybe even all) of them have problems with UX. It's not like end of the world, but sometimes it's just super annoying. Maybe you know such YouTube channel, where author describes such problems in many such softwares.
We can argue all day long, but I can just say from my experience it's much easier to use WYSIWYM type of editors, and more importantly it's much easier to develop them. Mostly because you don't need to worry about how to make everything as consistent as possible (for spacing between different elements, etc.)
Of course you need to learn commands, but it's not that difficult, and in a long term you can create scores even faster than using mouse.
And it's not only about speed and efficiency. For me, when I type the structure of my music gives me so much more pleasure, because it gives me feeling that I am writing music.
4. More precisely than any software to be honest. I can give you some examples that I've never seen:
Here you can see that stave lines don't intersect sixteenth beams, which allows to increase readability.
Or here, we optimize vertical spacing of dots for chords with whole tones.
Stave lines don't intersect text labels, which improves readability
In any other software, such ties for chords with whole tones would look ugly, but here we connect such chords quite nicely
And there are many such examples.
5. By "Using human language is the best way to do it", I meant that if we are going to use text to engrave music, then it's better to use plain language and avoid special characters.
6. "knowing English which is NOT an universal language; being optimistic, roughly 1/4 of the world population speaks it." I am aware that there are many other popular languages. But first of all, I am not trying to reach billions of users, for me it's important to create high quality product which is profitable enough to motivate me. This is my ambition. And second of all, I can adapt Unison for other languages as well, but it requires a lot of time as you can imagine.
I understand that music score as itself is a language, but it does not mean that we cannot use the language that we speak and write to digitalize it. We don't have music symbols on the keyboard, maybe someone in the future will invent it, but now we are limited in that sense.
7. I am planning to add MusicXML export/import, it of course will increase number of scores in Unison, and will increase speed of creating scores. Collaborations for teams of musicians is an interesting idea, that can be implemented in the future.
In general, I would say that Unison is more finished product than you may think, just check it out 🙂