News for hackers. Stuff that matters.

A comment on Mozilla and Unity Bring Unity Game Engine to WebGL. Parent comment

Re:Mozilla and Unity Bring Unity Game Engine to WebGL by withjive on Tuesday March 18, 2014 @12:21PM (#7422820)
They have already proved (Lego Starwars demo IIRC) that they can target the NaCL runtime for Chrome (and ARM Chromebooks). But I'm not sure when/if they plan to release that publicly.
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by doktrin on Tuesday March 18, 2014 @12:24PM (#7422838)
I think it makes more sense for them to aim towards some sort of unified platform. NaCL is cool and all, but it's very Google specific. WebGL is now even supported in the latest versions of IE.
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by TazeTSchnitzel on Tuesday March 18, 2014 @12:40PM (#7422979)
Yeah. Target asm.js and WebGL and you'll get Internet Explorer 11, Chrome, Firefox, IE and probably eventually Safari. With NaCl you get Chrome only. The choice is simple.
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by RussianCow on Tuesday March 18, 2014 @12:46PM (#7423040)
The choice wasn't so simple when asm.js was only supported by Firefox, and Microsoft had no plans to support WebGL in IE. :)
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by TazeTSchnitzel on Tuesday March 18, 2014 @01:08PM (#7423244)
asm.js is supported, inherently, by all modern browsers. It is just JavaScript, after all. However, only Firefox has a second compiler path especially for it. Chrome has some optimisations for asm.js-like code in V8.
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by RussianCow on Tuesday March 18, 2014 @01:36PM (#7423496)
Well, yes, but I find the WebGL port of the Unreal Engine demo (for example) unplayable without asm.js-specific optimizations. So by "supported" I really mean "optimized".
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by camus2 on Tuesday March 18, 2014 @05:34PM (#7425152)
a subset of a language is not the language itself. asm.js is not javascript.
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by gfodor on Tuesday March 18, 2014 @12:39PM (#7422968)
As a company they surely do not care if something is Google specific or not. They only care if they can sell enough licenses for it to make the development costs make sense. In light of chrome's adoption curve it seems to be a not terrible idea to target nacl.
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by Yorrrick on Tuesday March 18, 2014 @12:49PM (#7423066)
Or they could just target WebGL and asm.js, which already works in Chrome, and let's see how long Google sits around with Chrome being slower at a popular use case.
[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by withjive on Tuesday March 18, 2014 @01:38PM (#7423513)
Exactly, and it was also driven by the fact that it was easy for the Unity guys to get their existing toolchain building on NaCls LLVM toolchain. Now with ASM.js maturing, its another great opportunity.

Also we saw Unity developed a target for the Flash runtime (now with Flash pretty much dead, thats being shelved). Gotta give props to Unity for trying.

[ Parent | on HN ]
Re:Mozilla and Unity Bring Unity Game Engine to WebGL by krsunny on Tuesday March 18, 2014 @09:23PM (#7426274)
Wait a sec, are they saying the Unity5 webgl exporter will only work in firefox?
[ Parent | on HN ]