This is becoming not much more than some childish bickering and it's souring me on the potential Airspy purchase I had been contemplating for some time now - I understand the technical reasons at this point
why SDR# doesn't support SDRPlay, that's a given and it isn't difficult to grasp. Even the maker of the Frequency Manager+Scanner plugin suite for SDR# mentions something similar in one of the documentation files for his software (to bring it in line with SDR# build 1368 and the .NET 4.6 aspects) that with respect to SDR# any changes made to the app will more than likely break
his plugins and it's up to him to resolve updating
his software to work with SDR# when necessary.
I'm on the fence presently as to where to spend the money I've saved on a more capable SDR device than the trusty RTL sticks I've been using for close to 2 years now, and it's about time to get a move on things. I'd love to get a HackRF but that's still not within the realm of possibility for me but, an Airspy or an SDRPlay are definitely possible.
I've never really had issues with SDR#, and I personally still feel that the price of the Airspy is a bit high even in spite of the performance it offers but I can understand it's still generally a niche product when compared to the vastly more popular (and cheaper) RTL stick solutions even considering their limitations by comparison.
I suppose I need to look into SDRPlay and see what it's truly capable of, look for some comparison reviews for both devices and then go from there.
But honestly, to the creator(s) of SDR# and Airspy, all I can say is this:
You're not making it easy to support you if you're going to be childish in this situation. So .NET 4.6 is eventual and breaks things, so be it, but if people wish to continue using an older version of SDR# that works with SDRPlay, is it really that big of a deal to start tossing out accusations on Twitter? Seriously?
This is what comes to mind in this situation:
The appropriate response
Anybody else feel the same at this point?