|
|
Re: I may get flamed for this, but this IS the loony bin so... (Retroarch Bounty)
10/07/18 01:03 PM
|
|
|
> I'd be on this bounty like white on rice if it were better-defined what the end goal
> is.
>
> As I understand it, RA isn't an emulator itself but more of a frontend for other
> peoples' emulators, except with the emulators integrated at an API level rather than
> how something like a MAME frontend operates.
>
> Unless RA supplies a shared DRC/JIT system that the emulators all use, writing an
> AArch64 recompiler would ostensibly mean writing one for all of the possible
> emulators that have DRCs: Dreamcast emulators, N64 emulators, PC emulators, MAME, and
> so forth.
>
> If that is in fact the case, then while 1600 bucks is certainly not chump change,
> it's also still nowhere near commensurate with the amount of work needed to
> implement.
yeah, I saw this and thought exactly the same thing.
it pretty much highlights the entire problem with the RA design, and why anybody calling it an 'emulator' or even 'the best emulator ever' is seriously annoying because it's anything but, it's just a glorified frontend that annoyingly requires things to be compiled in a custom format just to use with it, stripping away any identity the emulators had and expecting them to work basically like a SNES would.
There's no sharing of emulation between modules, it's literally just other peoples work glued together as single system libraries, code duplication galore. It's the opposite of the design of a good emulator when you develop cores for actual components and make sure those cores work correctly with every system that uses them (and as such everything you emulate acts as evidence towards that)
It's the 'easy' option, but it isn't one that leads to better development which is one of many reasons why I continue to consider it a dangerous project.
|
|
Index 
Flat 
Re: I may get flamed for this, but this IS the loony bin so... (Retroarch Bounty)
Reply
