News for hackers. Stuff that matters.
Re:Mozilla and Epic Announce Unreal Engine for the Web by GotNothing on Wednesday March 27, 2013 @01:55PM (#5450938)
As soon as they find a way to put ads in it...
Re:Mozilla and Epic Announce Unreal Engine for the Web by notatoad on Wednesday March 27, 2013 @02:14PM (#5451053)
yes, because chrome is so full of ads...
Re:Mozilla and Epic Announce Unreal Engine for the Web by joshrice on Wednesday March 27, 2013 @02:11PM (#5451045)
on the loading screens!
Re:Mozilla and Epic Announce Unreal Engine for the Web by lucian1900 on Wednesday March 27, 2013 @02:15PM (#5451059)
Chrome has supported NaCl for a long time, which is quite a bit saner than asm.js
Re:Mozilla and Epic Announce Unreal Engine for the Web by hosay123 on Wednesday March 27, 2013 @02:36PM (#5451177)
You show up on every NaCl-related thread claiming it is awesome and asm.js is crap, but that's as far as it goes - you never explain why. You're basically wasting time because what you say is never actionable. Please defend your opinions - inform us!
Re:Mozilla and Epic Announce Unreal Engine for the Web by lucian1900 on Thursday March 28, 2013 @05:12AM (#5453885)
(P)NaCl exposes pretty much the same environment and tool chain devs get writing native apps. Predictable performance, decent debugging, etc. One can even decide to use platform-specific features if strictly necessary.

The problem it has is that it is largely opaque to the JITs in browser engines (even PNaCl, since JS JITs have nothing to do with llvm). One way to fix that would be to define a simple byte code as a compilation target and have people compile to that, in addition to compilation to JS with emacripten. The end result would be, in my opinion, much cleaner than the ugly hacks in asm.js

Furthermore, by design, asm.js will always need guards in the generated code, thus some overhead that can never be fully removed (although JITs will help with this). In particular, one can write "x = +x" in JS, but then change the type of x, thus invalidating the invariant. A guard will be needed to guarantee correctness, since asm.js is a subset of JS, but the outer set still exists.

It seems to me that web technologies are getting more and more crazy. To me it appeared obvious that asm.js is not a nice approach, but I can see many people disagree.

Re:Mozilla and Epic Announce Unreal Engine for the Web by BrendanEich on Friday March 29, 2013 @12:51AM (#5459288)
You are mistaken, there are no type guards within asm.js-verified/compiled/linked code. Read more at http://asmjs.org/.

/be

Re:Mozilla and Epic Announce Unreal Engine for the Web by gcp on Wednesday March 27, 2013 @02:37PM (#5451179)
You're too early for April Fools, but you almost got me.