> > The problem is nobody from the MAME Dev Team gonna release a MAME Android. Others
> > still building their ports in a shitty way. You guys can come up one better than
> > those shitty ones out there. There is no reason not to finish the source up for the
> > MAME Android. The source is there. But not finish.
> >
> > Don't want to continue working on it?
>
> The point is that Android is a shitty platform for emulation. It has TERRIBLE input
> lags and it requires a massive amount of work to port the whole thing to Android. So
> the cost vs benefits are not good at this point.
Not to mention that, historically, MAME ports to platforms other than the ones officially supported have mostly been the work of people outside of the main development team.
The fact that MAME currently builds on three main modern platforms (Windows, OS X, and Linux) from the same source tree is down to the efforts of people porting it from DOS to Windows, Mac OS (later OS X), and Linux then seeing their changes subsequently folded into the main branch. Until someone wants to go balls-out on an Android port that can be built from mainline source, it's probably not going to happen.
That said, all of the input, display, and other limitations and considerations of that platform will still apply. It really begs the question of why this is something being clamoured for when there are better alternatives available, and serves well to illustrate that just because you can do something doesn't necessarily mean that you should.
|
Index 
Flat 
Re: Mess with the RetroArch + MAME 0.187 last night.
Reply
Slamming the MAME 0.188 released at theiir face.
