I am Bill (WB4ALM) and I have been licensed for many years and was interested in Amateur Radio for quite a few years prior to being able to get licensed (Morse code was a major stumbling block because of the way my head appears to process "constant frequency" type sounds...)
Yes, it would be nice if we could go to "one place" to get assistance with software applications and some of the newer rigs, but that will probably never happen - there are two many different aspects of Ham Radio... Lots of people start to provide distribution support for one or more Ham Applications and then grow tired of the work it takes to keep those packages updated. The other issue is that there are too many distribution systems available for most application designers to become knowledgeable in more than one or two of them.
Now adding to that, every "version" of LINUX has its own way of using the standard Linux library directories. There have been attempts to standardize the usage, but not everybody follows the agreed upon "standards". Sometimes the software I install in a Linux system wants to be in "/usr/bin" and other times in "usr/local/bin". Now the software will run from either place, but those kinds of differences can sometimes make it difficult to resolve issues.
Under windows, well... it depends on what version of Windows and if the software is 32-bit or 64-bit, and under what version of Windows the software was originally created... Frequently I find that I must install Windows application software in its own directory on the C-drive, just because it needs to update its own configuration files. (Something no longer allowed inside the normal "application program directories" because of the destruction being caused by "HACKERS")
Program Authors also have a hard time keeping their applications running, because of the frequent changes to the internals of some Operation Systems - especially when an application needs to communicate with external devices like our radios and test equipment.
Up until just recently my primary Linux system was UBUNTU based, which I had been using for the past 16 years. Recent changes by Ubuntu's "staff", along with a few oversights, caused a major loss to me when I attempted an upgrade from UBUNTU 20.04 to 22.04.1
I have spent several months trying to recover lost files that were totally destroyed during the upgrade - yes, even the backup files, which were on a separate unmounted drive, were totally wiped out. A major loss to me was the loss of about 25 years worth of self-written software for me, my family, and my friends...
I was never able to get a reliable Ubuntu 22.04.1 system running even after multiple clean reinstalls of UBUNTU 22.04.1 -- and yet a clean install of LINUX MINT 21 worked perfectly the first time, and has been running reliably since mid-December 2022...
I, for one, happen to prefer Amateur Radio Digital communications and have found that it is best to contact the author(s) of individual programs when I need help.
One of the best-supported digital packages is FLDIGI and all of its "add-ons". The author (Dave, W1HKJ) and a very good group of volunteers have done an excellent job of keeping the packages updated and working. I have often used FLRIG to control my transceiver, even when operating in non-digital modes, and out-of-band support of other Communication services.
One of my EMCOM sidelines means that I have to run a windows based system for the required software. Every time WINDOWS does an update, I have to fix (and re-fix) the sound levels - it seems that Microsoft delights in changing everything that is "audio-based" to what they "think" are the best settings... ...and there is no way to say "keep your hands off my hardware, software and blinking lights."
With the sole exception of Video and Audio conferences (which are allowed to use the "default" Windows Sound System settings), I do --NOT-- use any of the windows supplied audio systems; all audio passed to and from my rig and the various software applications is via my SignalLink USB sound card interface, or via manufacture supplied USB connections. It is a real irritant that Microsoft constantly changes the volume settings and default devices settings every time they do any form of update processing.
I do create some Windows/Linux software for my own use, and I use a free "scripting" language (which is interpreted) called "ooRexx" that is distributed via sourceforge.net and supported by the Rexx Language Association (rexxla.org). The nice part is that my software will run under Windows, Linux, and many other operating systems without change.
While this version of REXX (ooRexx) supports programming in an "Object Oriented" fashion it also supports the "classic" or procedural style of programming (which is what I use). Both programming styles can be used in the same program, which is great when you want to use a "newer" function in an older program... And better yet, is that the language can interface with many other languages such as JAVA, and that some text editors and other applications use Rexx as an internal scripting langage for user-created macros.
As an FYI, The REXXLA group has just released the long-awaited version 5.0 of the language which can be downloaded from
https://sourceforge.net/projects/oorexx/files/ Version 5.0 of ooRexx comes with extensive documentation and can be easily learned by "non-programmers". (I know, I have taught it to teenagers aged 13 to 21.)
However, until such time as standardization actually occurs across operatings systems and platforms, I guess "google" or "bing" and all of the other Internet search machines would be your best bet to find support for the mode and equipment that you prefer to use. Don't forget that there are many email forums and Blogs that will (eventually) connect you with folks that have the same interests as you do....
In the meantime, for us folks that use Linux Mint, there is this forumn!