Surely this is a direct answer, and a very good one indeed.
For a senior representative of the development team to respond routinely to customer queries, provide helpful guidance, offer detailed insight into the philosophy and future plans of the program’s development, and even offer to do personal work such as reviewing scores, editing files, adapting templates and so on… these add up to a far higher level of customer service than I have ever encountered from any other software company. (Try making a similar request to, say, Adobe or Google and see what kind of response you get.)
To me, the fact that the team also engages directly with feature requests, often by saying “Thank you, you have a good point, and we will consider improving this behaviour in the future” is frankly amazing.
Of course it can be a bit disappointing to receive a response like that about something that you consider important. On occasion, it might seem that not only are OUR priorities FAR more obvious and important than everyone else’s, but that we also deserve to KNOW FOR SURE exactly WHEN and HOW those priorities will be addressed. But I think it’s also pretty clear how unfair that judgement is.
If I were you, I would give a friendly apology to Daniel for pissing him off, accept his kind and detailed responses as the end of the matter, and then either (a) enthusiastically await future improvements to the software, or (b) stop using the software, as you see fit.