News for hackers. Stuff that matters.
Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by stcredzero on Wednesday March 12, 2014 @03:08PM (#7387581)
For a high level managed language, 67% would be pretty godlike. There are some C programs that are less than 67% the speed of their own -O2 compilations. If 67% native speed winds up being the average efficiency, that's plenty good enough for the vast majority of computing.

As recent history has been teaching us, doing more with less has mainly to do with getting more mobile, distributed, and ubiquitous. We're quickly reaching the point where that means something even "smaller" than a web browser.

EDIT: Could WhatsApp be the 2nd coming of WAP?

Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by taeric on Wednesday March 12, 2014 @03:34PM (#7387742)
You ignored my 200% mark, though. If I could run this demo in the browser and it pegs all of my cpus, compared to running the same demo "native" and having half my system capable of idling, I'm not sure I see the win. Even if it gets to 100% of "native." (I hate that it sounds like I am claiming that is the case here, as I really don't know.)
Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by azakai on Wednesday March 12, 2014 @05:56PM (#7388656)
> I'm not sure I see the win

For a user that can install a native build, the native build will run better. No doubt. But, most users in the world do not know how to install apps, and even if they did they shouldn't because of security concerns.

For that reason, game devs know that asking people to install a plugin or a native build will kill off most of the potential users of their game.

Instead, if you just give people a link to click and it jumps right into the game, that will maximize the amount of users able to play it. This is the main reason for the anti-plugin and pro-web movement in games.

Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by null_ptr on Wednesday March 12, 2014 @06:40PM (#7388902)
Oh, so native programs are the boogey man now, huh? I don't know where this whole push for Everything Must Be JS comes from, all it does is waste electricity maxing out Core i7's running some raster demo from the 80s.
Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by epsylon on Thursday March 13, 2014 @05:49AM (#7390834)
> But, most users in the world do not know how to install apps

That's a ridiculous claim.

> if they did they shouldn't because of security concerns.

Equally ridiculous. All the new shiny HTML5 tech is also bringing its load of security issues and an ever-increasing attack surface as the Web Browser slowly transforms itself into an OS.

There's a valid reason for running small games into the browser, but there'll never be a good reason to do that for a performance demanding game.

Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by stcredzero on Wednesday March 12, 2014 @05:23PM (#7388497)
A game like this is a singular and extreme case. I can see a really big win for lots of business software. With browser deployment, lots of logistical problems just disappear. Heck, the notion of traditional corporate structure starts to disappear: Corporations exist because they can provide lowered transaction costs in specific contexts of production.

I'm not sure I see the win. Even if it gets to 100% of "native."

Even if Unreal engine FPS don't get to 100% of native, that doesn't preclude the disruption of lots of other software distribution models, including entire subgenres of games. But it goes much farther than just games.

Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by taeric on Wednesday March 12, 2014 @06:26PM (#7388823)
How does this accomplish anything that Steam isn't already accomplishing, though? I have only bought humble bundles, and I already have a couple of hundred games on Steam. Tempted to buy more.

And I don't own a windows machine.

Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by stcredzero on Wednesday March 12, 2014 @07:18PM (#7389084)
How does this accomplish anything that Steam isn't already accomplishing, though?

Browser based distribution has the potential to have better security than Steam currently has. Of course, Steam could implement those things as well. It could well be that Steam or something like it will win over the browser.

Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by taeric on Wednesday March 12, 2014 @07:40PM (#7389172)
I don't see how a browser based distribution has the potential to be better as far as security. I don't think it is foregone it would be worse, mind.

What does a browser by in terms of added security? Encrypted connections did not spring in to being with ssl. And, doing a secured stateful connection seems easier/better than the stateless messages method of traditional http applications.

Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by stcredzero on Wednesday March 12, 2014 @08:32PM (#7389388)
Please re-read. Browsers don't have exemplary security, but, what they have can be slightly better than simple code signing. Also, I say it's entirely possible that the other platforms to leapfrog them. The problem with current sandboxes for native code, is that they disarm the participants while empowering malicious code.
Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by taeric on Wednesday March 12, 2014 @09:54PM (#7389668)
I am rereading. I am also asking for specific examples of how a browser has potentially better security than a custom application. Because, I just don't see it.

Unless you are trying to say that something in a limited sandbox of a browser has limited capability outside of said sandbox. But... how is that not just as true of any other sandbox approach.

Re:Mozilla and Epic Preview Unreal Engine 4 Running in Firefox by stcredzero on Friday March 14, 2014 @02:33AM (#7397287)
Right now, native code security is pretty much limited to code signing and sandboxing. Browsers go one better than code signing with restriction of communication. Additionally, entire classes of exploits are made much harder because Javascript is a managed language.