Now that is just pure sarcasm aimed to be derogatory. I would have thought a "hero member" would have been above that. I have tried to be polite, and I have tried to help the community, but when I call you out on being rude, you just become more so. You should be ashamed of the way you are talking!
Yes, Windows has primarily handled file extensions using the last three characters of a file name, but there are exceptions to the rule. For a start, .html, .jpeg - windows has not been locked to 8.3 since Win95. That is more than two decades ago that Windows broke away from DOS limitations. Back in the old days Windows *had* to call those files *.htm and *.jpg, and one of them stuck, but the other didn't, because people found *.jpg easier and there was no need to keep the longer version and the rules had changed. But *.html was definitely an exception to the old 8.3 rule that is now ubiquitous. We are not limited by 8.3 because technology has moved on. Now we also have *.docx, *.xlsx and more. Now you can also have long file names and spaces and that is all accepted.
That is like grammar - you would be hard pressed to find a language that does not break its own grammatical rules at times because grammar is a snapshot of usage at a given time, and usage changes, so grammar has exceptions, and then with time the snapshot incorporates changes. The grammar purists argue over the exceptions, but every year dictionaries incorporate new exceptions as accepted grammar and eventually even the purists stop arguing over what had been common use for years. The exceptions stay, and people know that in 99% of cases it happens this way, but in 1% it happens that way, and that way is OK, because grammar has caught up with actual use.
Double file extensions have been around for decades. *.tar.gz has been around for decades. It is unusual, but it is accepted. People use it all the time. They understand that both the tar and the gz mean something about the type of file that it is and the processes that it went through to become what it is. Some people have used *.tgz instead, partly because of the old 8.3 rules, and partly because it is easier, and that is fine, but the *.tar.gz double extension is still the dominant accepted file extension for that sort of file. People understand and accept that someone decided on a naming schema for that sort of file a long time ago, and that it means something, and so that is good enough for them. It is unusual, but it is technically feasible and it is logically feasible to have a double file extension. It is allowed.
Now the designer of lossywav and lossyflac designed a new standard that augments an old one. He put it up on hydrogen audio, just because he chose to, including the naming schema. He also put the naming schema in the source code. Those who choose to use lossywav / lossyflac would normally choose to follow. It is technically feasible on any platform. It is logical that the files have a double file extension. We are not limited by 8.3.it is allowed and, in fact, useful. The double file extension was settled on to alleviate concerns of the community that people might not be able to distinguish files that have been through the LossyWAV process prior to being encoded as flac. The audio purists would riot if there was no way to distinguish flac from lossy flac. In fact, even after the double file name convention was announced, it took a long time to convince the purists that everything was going to be OK, and that they could go back and distinguish their own rips, but more importantly they could distinguish other peoples rips. It is about clarity, about choice, about purity, about fidelity. All that stuff is important to a large portion of the audiophile community, whether they use it or not they want it to be able to be done, and there was much said about it until in 2007 or 2008 it was settled that the double file extension was the official way to safeguard flac while distinguishing lossyflac. The argument is over for the audiophiles and has been for a decade.
Now, many years later, a program starts using that standard. It did it well when encoding, but it removes the distinguishing file extension when moving files and renaming/organising them at the same time. This is something that could cause confusion, and therefore it is not preferable. It is something that is technically feasible, and easy to fix. It is allowed by every platform, *even Windows*. We are not limited by 8.3 anymore.
So really, what is the issue here?
It is not a technical issue - it is dead easy to incorporate into the MusicBee code
It is not a logical issue - the double extension is a rational explanation of the sort of file it is and it distinguishes files to safeguard purity for those to whom it matters
It is allowed by every platform - we have not been stuck with 8.3 for decades, thank goodness! I want my long file names!
I don't get why this is so offensive to you that you have to disprove it.
This is in usage, and has been for a decade. It is an accepted standard by the audio purists, who are some of the most difficult people on the planet to convince - and who you would hope can find a home with an app like MusicBee.
So why is it a problem? Really?
The question to ask is, is there a genuine use case? Is there a segment of the community that might want this? Is it hard to do? Will building this in cause problems for other functions? It might not be for everyone but I think if we get away from the polemic and think about use and technical issues, the answer is obvious.
The answer is, why not?