Changes
Jump to navigation
Jump to search
→Controversies
Some of those products have attracted the ire of parts of the emulator community over issues not necessarily related to the product's quality, but ones related to open source emulators. In some cases, it's because negotiations with open source emulator and/or frontend developers fell through and the company used a "lesser" option as a replacement. In others, an arrangement was reached, contracts and money were exchanged only for the project maintainers to turn out not to have gathered the complete consent of all contributors, some parts are licensed as a strictly non-commercial license, and similar issues. Sometimes, it might have to do with an incomplete source code release from companies that have to abide by GPLv3 obligations. And of course, the company might be acting malicious towards emulator developers.
Since the problem with these is primarily a meta problem that doesn't have much to do with the product's actual quality, and is a controversial subject even within emulator developer circles (some well-known developers such as byuu did eventually agree to work with the likes of Hyperkin, after all) this section is about listing some of those cases.
* Capcom Home Arcade: Capcom has licensed (with compensation) FinalBurnAlpha from the project's maintainer, however this has lead to some [https://www.google.com/search?q=capcom+home+arcade+illegal&oq=capcom+home+arcade+illegal controversy] and outrage by fellow FBA developers (who didn't agree with this move, and eventually made their own fork) and MAME developers (where some of FBA's code comes from), as FB Alpha's license isn't cleared to allow for commercial use and many of those developers think the FBA's license is an ugly mess of contradicting licenses that should not exist.
