[1]: https://lakka.tv/
Retroarch is a frontend for libretro, which provides a set of APIs that emulators can use for I/O. If you can produce a library from an emulator that conforms to the APIs, then you've got what Retroarch calls a "core".
Thus retroarch acts as a kind of target for emulators, that lets them all use a common frontend, including for things like button mapping (each emulator maps to a set of "fake" Retroarch inputs, which Retroarch then maps to your actual controller) or video output/filter settings.
This is a different approach from other meta-emulators that typically invoke full, independent emulators as if running them from the command line, and try to manage them externally.
And yes, there are multiple mame cores for Retroarch:
https://github.com/search?q=libretro%20mame&type=Everything
[EDIT] Also, I've run Lakka on hardware as weak as a Raspberry Pi 2. You can't use fancy video filters (say, to make games look the way they did on a CRT TV or monitor) but it'll run a whole bunch of Mame games, plus all 8-bit console games and most from the 16-bit era at acceptable frame rates and latency. It also worked well enough to be comfortably playable for a surprising number of Playstation (PSX/PS1, the first one, that is) games and for exactly one of the N64 games I tried on it (Super Mario 64—all other N64 games were a lag-fest, if they ran at all, but that one was smooth and snappy). Any mini PC from the last 10 years is probably more powerful than an RPi2, so should do even better. RPi4 takes that "most" on the 16 bit era and makes it "all" and makes a bunch more N64 and Playstation games playable. Probably many Playstation 2 games as well, but I've not tried it.
Is this really necessary? Why not map input devices directly to core inputs? Makes configuration needlessly complex in my experience.
It's less complex than a wrapper program having to know a bunch of different config formats and conventions.
Again, cores run as shared libraries inside Retroarch. These "fake inputs" aren't, like, actual OS-level simulated devices. It's more like a core listens for events of type (name made up) "ra_analog_0" and treats anything coming in as left-stick x-axis positive-direction input, and by convention so do most or all other cores that emulate a system with a left analog stick (or perhaps with just one), unless they have a good reason not to, so default Retroarch-provided automatic input device mapping can make most common gamepads do something sensible with most cores, as soon as you connect them. Then if you prefer to swap left and right sticks, you do it one place and it works everywhere. Or if you prefer to swap left and right on just one game, you do that. The core never has to know about any of it.
Now you only have one place to go remap buttons, rather than N.
(That would be my guess, anyway.)
I run it on some old quad core amd HP thin PC. Plays all non-3d games perfect.
Also look into a Mister. Not a mame cab but tons of arcade games and consoles. That’s my “ass in seat” gaming rig.
This is not necessarily a feature; actually I consider it an anti-feature, as one is forced to chase the romset versions (either download the full set, which nowadays is tens of GBs, or the diff, which I've never tried).
If one actually plays games, and they play correctly, there's no value in upgrading the emulator and ROMs to new versions.
I think this is not exact, as, if memory serves me well, I had breakages with existing romsets when upgrading MAME.
While a romset itself may not change, another one may take the place of the default set, and the previous gets renamed, so it requires manual intervention.
I used to play with MAME games - not hundreds, but I think a few tens, and the hassle of upgrading was never worth, with I think only one case where upgrade was required.
So, YMMV. My suggestion for casual users is that if one has a given set of favourite ROMs, and they work, there's no reason to upgrade.
That will update it and download the mame Roms from archive.org. You will need a de-10 nano, sdram card, and a usb otg hub. I also have a Wi-Fi and a Bluetooth dongle. Works amazing. New PSX core is 90% there. Saturn is coming too, but no ETA
You run an updater script which pulls in all the stuff.
The drawback to RetroArch is that the UI is non-intuitive and it's a bitch to configure.
I just want to download an OS image, write it to a USB stick, put my ROMs on the stick, put the stick in my mini PC, and boot it up and play.