MAME and MESS Officially Merge into One Unified Emulator
On May 27, 2015, the MESS project — which had emulated computers and consoles separately from MAME's arcade focus for over a decade — formally merged into MAME, realizing a unification effort that had been prototyped for years.
On May 27, 2015, MESS (Multi Emulator Super System) formally merged into MAME, unifying two long-parallel emulation projects that had, for over a decade, covered different hardware under the same underlying codebase but separate public identities.
What MESS covered that MAME originally didn’t
Where MAME’s original focus was arcade boards specifically, MESS extended the same underlying emulation framework to home computers, game consoles, and a wide range of other obscure historical electronics — by April 2015, immediately before the merger, MESS supported 994 unique systems across 2,106 total system variations.
The unification effort that preceded it
The formal 2015 merger wasn’t the first attempt at bringing the two projects together — developer David “Haze” Haywood created an experimental build called UME (Universal Machine Emulator) between 2011 and 2014, specifically to prove out what a single program emulating both arcade hardware and home systems together would actually look like. UME served as a working prototype the eventual official merger could build directly on, rather than the unification happening as an untested, single leap.
What changed for users after the merger
Post-merger MAME includes the entirety of what MESS supported, plus the hundreds of additional systems added to MAME in the years since — meaning the historical distinction between “arcade emulator” and “computer/console emulator” mostly stopped mattering from a user’s perspective, with one unified program and one unified set of release notes covering both.
Why unifying the codebases mattered beyond just convenience
Arcade hardware and home computer/console hardware share a great deal of underlying emulation infrastructure — CPU cores, sound chip emulation, display timing — that had been maintained essentially twice, once in each project, before the merger. Consolidating that shared infrastructure into one codebase reduced duplicated maintenance effort considerably, letting improvements to a shared CPU core or sound chip emulator benefit both the arcade and computer/console side of the newly unified project simultaneously, rather than needing to be ported between two separate codebases by hand.
Sources: Multi Emulator Super System — Wikipedia, MESS: The Multi-System Emulator and Gave Birth to Modern MAME — InsertMoreCoins