MAME Running In Chrome [Slashdot]

[DP ServBot]

http://feedads.g.doubleclick.net/~at/M84BZrNL5uTynB67up2WroQe8CU/0/di (http://feedads.g.doubleclick.net/~at/M84BZrNL5uTynB67up2WroQe8CU/0/da)
http://feedads.g.doubleclick.net/~at/M84BZrNL5uTynB67up2WroQe8CU/1/di (http://feedads.g.doubleclick.net/~at/M84BZrNL5uTynB67up2WroQe8CU/1/da)

An anonymous reader writes to point out this interesting outgrowth of Google's Native Client: a Google engineer has ported MAME 0.143 to the browser-based platform, and written about the process in detail, outlining the overall strategy employed as well as specific problems that MAME presented. An impressive postscript from the conclusion: "The port of MAME was relatively challenging; combined with figuring out how to port SDL-based games and load resources in Native Client, the overall effort took us about 4 days to complete."http://a.fsdn.com/sd/facebook_icon_large.png (http://www.facebook.com/sharer.php?u=http%3A%2F%2Fgames.slashdot.org%2Fsto ry%2F12%2F01%2F01%2F0148246%2Fmame-running-in-chrome%3Futm_source%3Dslashdot%26utm_medium%3Dface book) http://a.fsdn.com/sd/twitter_icon_large.png (http://twitter.com/home?status=MAME+Running+In+Chrome%3A+http%3A%2F%2 Fbit.ly%2FrDVXAa)

Read more of this story (http://games.slashdot.org/story/12/01/01/0148246/mame-running-in-chrome?utm_source=rss1.0moreanon&utm_medium=feed) at Slashdot.

http://feeds.feedburner.com/~r/Slashdot/slashdotGames/~4/_HMzl6fS2VE

More... (http://rss.slashdot.org/~r/Slashdot/slashdotGames/~3/_HMzl6fS2VE/mame-running-in-chrome)

[Ze_ro]

So, Chrome's "Native Client" stuff is basically just the ability to run x86 code through the browser. It's not emulating or translating anything, it just passes it to the hardware.

Usually the point of porting something to a browser (ie, HTML5 or *shudder*... Flash) is to make it multiplatform and easily accessible... but all this really does is needlessly tie the application into a browser windows.

Kind of a nifty hack I guess, but ultimately pointless.

--Zero