It kind of reminds me of the periodic declaration someone makes on HN that textual programming sucks and we all need to switch to something else, usually visual programming in this case.
If someone takes time to deeply understand the advantages of the textual approach and then builds an alternative, I'll listen.
But at this point, anyone who is doing this and their criticism of the original approach is shallow and uninsightful, where it's basically just "it's old and it must therefore suck", is unlikely to produce a good answer.
I think that applies to the music notation case too. "Conventional" music notation isn't just a staff and a couple of types of notes. By the time you handle all the use cases that conventional notation handles, or even just a solid subset of it, your brand new notation is probably a lot less elegant than it started out as in someone's head.
If someone takes time to deeply understand the advantages of the textual approach and then builds an alternative, I'll listen.
But at this point, anyone who is doing this and their criticism of the original approach is shallow and uninsightful, where it's basically just "it's old and it must therefore suck", is unlikely to produce a good answer.
I think that applies to the music notation case too. "Conventional" music notation isn't just a staff and a couple of types of notes. By the time you handle all the use cases that conventional notation handles, or even just a solid subset of it, your brand new notation is probably a lot less elegant than it started out as in someone's head.