Flex DumbSDr is useless for many that want to really make adjustments- esp on CW (side tone ring a bell- or is that still deaf)
While Apache Labs based there early success off of PowerSDr an open source code written by Flex there are many rumblings in the Apache world since Ritchie stopped writing code
Which brings me to the why I don't want to see EESDR go open source.
Apache had to many folks writing code and things got messy, now there are few doing anything with the PowerSDr side of things. Hence Thetis seems to be were most of Apache users are moving in terms of software.
By EESDR keeping it in house: things don't get messy and the code is cleaner, which is one reason why the CPU usage of EESDR is much less then the others, bad coding. multiple lines of the same things redundancy-eats processing
What is like Apache one of the more common coders decides to leave or perhaps place some bad coding (backdooring etc.) in because they get pissed off.
EESDR is using QT6 now for V3- that is a very good move since it makes moving forward with new versions quicker and less troublesome especially since it can be applied to all the platforms.
As far as Support Joesi- by community they get much feedback and I will say unlike another company they acted on it. There open and responsive to the community.
While yes open source has it place, I personally don't see a good move for that with EESDR- software- another thing keeping it in house means they will attend to issues and come up with new things in order to self promote there abilities they then have a goal-(paycheck/job)
I'll second Tom: of all the SDR radios and applications for them, I have used and been around EESDR is easily my #1 pick.
Another thing making it open source can eventually do- Eat up development time and the abilities to put out new software- as it becomes a logistical pain in the ass, and fighting over what should and shouldn't be in releases, feelings get in the way of coding and shit rolls downhill.