ludo VS macdriver

A similar project is Ludo [1] which is part of the libretro family. More for emulation but really a clean UI (it actually has screenshots)

[1]: https://ludo.libretro.com/#about

Linux Mint is fine. You'll want to modify it to start using something lighter than Cinnamon (I suggest OpenBox); 4GB of RAM means that KDE and GNOME/Cinnamon are not going to be fun, and as you're using it for arcade games, you don't need much more than a launcher for Steam/RetroArch/EmulationStation/Ludo/Lutris/etc.

Have a look at https://ludo.libretro.com/ if you can't work out RA.

Ludo is better than both.

MULTI EMULATORS (basically one program that handles a bunch of consoles) I would advise you to avoid frontend or multi emulators like mame or retroarch, because they could be intimidating if you start in this area to start with a frontend multi emulator, I recommend this one witch is beginner friendly and have a good documentation ludo emulator

There's a spin-off of Retroarch that I think is way better called Ludo. It's basically a less confusing version of Retroarch with a really clean UI!

did you try retroarch? if you want something simpler, give ludo a try. It's from the same team, but made simpler. https://ludo.libretro.com/

I highly recommend Ludo, it's like Retroarch but much easier to use and automatically chooses the best emulator for each system. Just put in your roms folder and it'll automatically split them by console, then just choose and play.

You just want Ludo. Go use it.

[You might like Ludo](https://ludo.libretro.com/

The first big release of the year was the macdriver project, which got a significant response on Hacker News. It gives us Objective-C and Apple framework bindings for Go, letting you build simple Apple apps entirely from Go. That wasn't possible before, so it was a little exciting, but it was early. The native Go APIs included for commonly used Foundation and Cocoa classes were far from complete. They could still be used if you knew what you were doing, but with an ideal of total coverage of Apple frameworks, that wouldn't be enough. There were also unresolved issues just deciding how to best manage memory and pointers, which I knew would fall on me to figure out and take some time.

Even less common are schemas for non-web APIs. In 2016, Electron started releasing a JSON schema of all their APIs that allowed me to build a bridge to use Electron APIs from Go. I had that prototype in mind when I started the macdriver project that was released a couple months ago. Right now we're manually wrapping Apple framework classes with Go types so you can write native Apple platform applications that look like this:

It started as a demo for macdriver, but over the last week or so I've been making a standalone version. 90% of that time was playing around with it while trying to make demos.

Done https://github.com/progrium/macdriver/issues/12