Linked by Thom Holwerda on Thu 3rd Oct 2013 22:25 UTC
Mozilla & Gecko clones

Whether or not the Open fits your needs, one thing is clear: Mozilla needs more capable hardware to demonstrate Firefox OS' potential. The Open is good for someone whose alternative would be a basic flip phone, but the camera quality, connectivity, display and performance don't do full justice to the software.

A promising start, but clearly better hardware is needed. I'm really hoping Firefox OS gets a fair shot.

Thread beginning with comment 573866
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Don't care much for it
by Kroc on Fri 4th Oct 2013 11:50 UTC in reply to "RE[2]: Don't care much for it"
Kroc
Member since:
2005-11-10

It's not porting, it's compiling. "Porting" would imply that you were re-implementing the same reference design in JavaScript rather than cross-compiling existing source in another language.

Reply Parent Score: 3

lucas_maximus Member since:
2009-08-18

they are used interchangeably.

Reply Parent Score: 2

RE[4]: Don't care much for it
by cdude on Fri 4th Oct 2013 21:14 in reply to "RE[3]: Don't care much for it"
cdude Member since:
2008-09-21

It's not porting, it's compiling


https://blog.mozilla.org/blog/2013/03/27/mozilla-is-unlocking-the-po...


Mozilla has been able to bring Epic’s Unreal Engine 3 to the Web. With this port, developers will soon be able to explore limitless possibilities when it comes to porting their popular gaming titles to the Web.


And its not an easy port if you need to consider performance too.

Edited 2013-10-04 21:17 UTC

Reply Parent Score: 1

lvl21ogre Member since:
2013-07-04

It's a port, but it's not a port in the sense that they re-wrote Unreal from scratch. They compiled their code down to Javascript using LLVM modules, so they wouldn't have to deal with JS directly. ASM.js is an optimization in the browser runtime to help address a lot of performance issues, though it's still young and there are a lot of problems left to solve (not the least of which is the relative bloat of compiling into a machine-created JS file instead of a size-optimized binary file). Whether it works out or not is just as nebulous as any other similar technology trying to run "native apps" in the browser.

Reply Parent Score: 2