It is also important to not introduce changes at a high rate. To keep software stable on a number of different platforms, it is important to keep a small codebase with a good test coverage. Why not implement Ludo as a menu driver in RetroArch? It definitely shares a lot of the same core values. It also shares some of the same developers, as kivutar is an important contributor of the libretro team, and all the people who provided help have also been members of the Libretro community.
Same cores, similar UI patterns, joypad driven UI, same game thumbnails, mostly the same game database, same terminology. Like RetroArch, Ludo is a libretro frontend, so the way of communicating with the emulators is the same. The cores are packaged in the frontend so no additional step is required to launch a game. For example we support less cores, and choose cores for the user. Ludo will stay smaller than RetroArch by only implementing the core features and by targeting less platforms.īy not adding advanced functionalities, we aim to deliver a stable frontend for beginner users on Windows, Mac OSX and Linux. Frequently Asked Questions How is Ludo different from RetroArch?
