5 ms·
This is neat and all, but I wonder if things are really better moving to "in the browser." The discussion is of "upwards of 60% as fast as native." Is this us
by taeric 13y ago
This is neat and all, but I wonder if things are really better moving to "in the browser." The discussion is of "upwards of 60% as fast as native." Is this using the same amount of processing power as native, or is this "67% as fast as native, using 200% of the CPU as a native solution?"
I mean, I realize that processors and machines are only getting more capable. It seems silly to start requiring faster and faster processors to achieve what slower ones could have achieved. I would rather we just kept achieving more.
- stcredzero 13y agoFor 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?
- taeric 13y agoYou 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.)
- stcredzero 13y agoA 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.
- taeric 13y agoHow 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.
- stcredzero 13y agoHow 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.
- taeric 13y agoI 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.
- stcredzero 13y agoPlease 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.
- taeric 13y agoI 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.
- azakai 13y ago> 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.
- null_ptr 13y agoOh, 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.
- epsylon 13y ago> 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.
- MichaelGG 13y agoEspecially considering that asm.js isn't really using a JS execution engine. You can smuggle a low-level machine code via any mechanism. As I understand, without asm.js specific optimizations, it doesn't really work. I know, it's a cute way to get some movement without the political nightmare of having to decide on a proper VM for the web. Since it's "just JavaScript", other browsers will run but be really slow, leading users to blame the browser. At least, I guess that's the idea. It's still a shame they have to resort to such tricks.
- chc 13y agoIt is true that most other browsers don't have special compilers for asm.js, but they still tend to get pretty good performance out of it.
- stoptalkingshit 13y agoOf course they do! asm.js is a collection of everything in Javascript that optimizes on the current hardware. It's not the least bit dynamic, i.e. it is not Javascript.
- nawitus 13y agoAnd if you run that code in a non-asm.js browser, it'll still be compiled to native code if the application benefits from it.
- meritt 13y agoThe same can be said for all development over the past 15-20 years. The reality is development time and cost is drastically lowered when intermediate developers can produce working software with minimal consideration toward optimization, lowering resource usage or decreasing overall package size.
- taeric 13y agoAnd better tooling helps here more than anything else. The giant elephant in the room nobody likes to speak towards is that Flash dominated not because it was a great language, but because they had awesome tooling around it. This is doing very little to address that. Now, the Unreal Engine is a great tool in and of itself. Having it target the browser is the questionable part to me.
- cwyers 13y agoIf you look at the browser makers who primarily target operating systems other than their own (Safari doesn't count, as Safari for Windows is mainly a developer tool, not a product; and Opera doesn't count, as it's now based on Chrome, rather than being its own), they're pushing heavily for the browser to be the userspace, both in terms of shipping an OS based around their browsers (ChromeOS/FirefoxOS) and shipping apps to current OSes using their browsers rather than native code. This demo may focus on the high-end graphics, but I doubt that's the reason anyone is investing effort into this. Mozilla wants cross-platform mobile games on Firefox OS, and Epic (I'm guessing) wants to be able to run games on Firefox OS/Chrome OS/Sailfish/Tizen/Ubuntu Touch/flavor-of-the-month that supports HTML 5, as a long-term hedging of bets. Not all of those explicitly support asm.js, but Chrome is going to get better at supporting asm.js even if it never gets to feature parity with Firefox, and the non-iOS world is likely to be running a derivative of Chrome or Firefox.
- taeric 13y agoSo, if you look at the four main browser vendors... Well, two of the four browser vendors, you will find that browser vendors would like to extend the reach of the browser. Not sure how that is surprising. The argument for wanting to target all of the platforms seems nice. Except the major tooling companies that want to target multiple platforms have already learned how. Seeing games come out on PC, Xbox, and Playstation is proof enough of that. So, again, what does this buy that the tooling does not already support? Especially if you simply design things such that they can be cross compiled with C.
- mixedbit 13y agoGames performance is often GPU bound. If a driving language (C++, JavaScript of whatever else) is fast enough to compute application logic without delaying frames, it doesn't really matter if it is x% slower compared to some other language. GPUs in WebGL are programed using native shaders so there is no performance penalty for GPU computations.
- taeric 13y agoThen explain the "within X% of native" from the link. If this demo is strictly limited by the GPU, then why isn't it as fast as native, period?
- mixedbit 13y agoThe X% from the link is not about performance of the demo, but about performance of asm.js: "In less than 12 months, optimizations have increased the performance of Web applications using asm.js from 40% to within 67% of native, and we expect it to get even faster". To me such number doesn't mean much, it most likely refers to some micro benchmark that achieved 67% of native performance.
- corysama 13y ago67% native speed == 1.0/0.67 native processor requirement == 149% CPU compared to native solution.
- taeric 13y agoApologies for not responding. The post above talking about how this wasn't necessarily referring to frame rate basically hit my misunderstanding on the head.
- azakai 13y ago"67% of native speed" means that for a fixed CPU workload, it will take 1.5 times longer to run. Of course this depends a lot on the benchmark, some run better and some run worse. Note also that this is on the CPU. On the GPU, WebGL is already extremely close to native GPU speed.
- taeric 13y agoThe fixed CPU workload makes sense. I mistakenly took it to mean they simply got within 67% of the framerate of native. Mayhap my misunderstanding is even deeper and those mean roughly the same thing. I'm still not sure I see the compelling use case. The tooling to create games that target various platforms already exists. Does this really widen the ballpark?
- azakai 13y agoMeasuring performance by framerate is tricky actually - it usually maxes out, and it's an inverse value, etc. It's a good quick measurement perhaps ("game X gets 50fps in Y but 60fps in Z", then clearly Z is better) but it's not an accurate measurement in many senses (for example both could get 60fps but one might use less CPU cycles). Measuring execution time for a fixed, deterministic non-stop workload is the best thing in my opinion.
- taeric 13y agoMakes sense. I still have to squint to really see the benefit here. :(
- stcredzero 13y agoThe web has always had the best discovery mechanisms. The problem endemic to Steam and the App Stores has been poor discovery. Good discovery mechanisms mean better information flow in the market, which generally means more innovation and consumer benefit. But if the walled gardens get really good discovery, they would win and deservedly so. As it is, they smell a bit too much like crony capitalism.