Also, RetroArch is a very powerful and sophisticated frontend, and one of the common criticism is that it exposes too many configuration options for the average retro gamer. RetroArch is an extremely active project and has a growing codebase that makes it harder to reach stability. It is also important to not introduce changes at a high rate. To keep a software stable on a number of different platforms, it is important to keep a small codebase with a good test coverage. Why not implementing Ludo as a menu driver in RetroArch? I think we can also say same developers, as I am an important contributor of the libretro team, and all the people who provided me with help are also member of the libretro community. Same cores, similar UI patterns, joypad driven UI, same game thumbnails, mostly the same game database, same terminology.

The cores are packaged in the frontend so no additional step is required to launch a game.Īs RetroArch, Ludo is a libretro frontend, so the way of communicating with the emulators is the same. Some design choices are different, for example we support less cores, and choose cores for the user. By not adding advanced functionalities we aim to deliver a stable frontend for beginner users on Windows, Mac OSX and Linux. Ludo will stay smaller than RetroArch by only implementing the core features and by targeting less platforms.

Launchbox mac emulator