I cant help but think every time I read this, that a significant number of potential JRiver users seeing this must walk away and look for something else that will do what they want.[...]
Please don't refer me to the various threads why because I've read them, and they are the past. I'm interested in the future.
If you haven't read the thread or threads in question, here's a quick summary:
JRiver has spent a ton of money on several projects like this and have been faced with their work becoming totally useless. So it was completely wasted money for them. In particular, Tidal would not approve the interface that they wrote. So they are stuck in a situation where Tidal won't allow them to integrate and they wasted money doing it.
This also leads to JRiver not wanting to do more projects like this in the future because another company can control their fate. A simple change of API on the provider end would render JRiver's interface "dead" and useless. ...and if that company isn't willing to work with JRiver, then it's dead forever.
I think what I've said reflects what Jim has said in the past. I'm sure he will correct me if I'm mischaracterizing his experience and opinion.
I do agree that it's too bad that things are this way. I personally don't use streaming and likely never will. I disagree with it in several philosophical ways that I won't bore you with. But just about everyone I know that likes music is interested in some streaming service. THey are certainly popular.
Brian.