Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by njharman on Friday August 12, 2011 @01:18AM
(#2876094)
Meh, very few apps are cpu constrained. For vast majority targeting html5/javascript and it's mindboggingly huge installed base is a bigger win.
[ Parent
| on HN ]
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by nitrogen on Friday August 12, 2011 @02:48AM
(#2876244)
Meh, very few apps are cpu constrained.
One must be very careful making statements like this. The only reason you're not seeing CPU-constrained webapps is because they aren't being created, because they would be constrained by the CPU. For example, I'm writing an app that would be significantly better if I could do fast client-side processing of data. Eventually I plan to use WebGL shaders, but I don't know if GLSL shaders can actually do what I need to do.
Your second sentence, however, is reasonable.
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by cageface on Friday August 12, 2011 @02:26AM
(#2876206)
This could, at least in theory, make it possible to deliver on the web a serious competitor to Photoshop, for example. I don't see that happening any time soon in Javascript.
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by ootachi on Friday August 12, 2011 @11:34AM
(#2877673)
You assume wrong. Modern tracing or type-inferring JITs are heavily optimized for the kinds of tight loops you see in image processing.
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by cageface on Friday August 12, 2011 @07:26PM
(#2879674)
All the heavy lifting in apps like that is done in SIMD.
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by ootachi on Friday August 12, 2011 @10:28PM
(#2880050)
Which doesn't require NaCl. https://bugzilla.mozilla.org/show_bug.cgi?id=644389
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by leon_ on Friday August 12, 2011 @04:11AM
(#2876403)
> Meh, very few apps are cpu constrained.
Maybe on the server side. Client side is a different story. My machine is regularly hitting 100% usage when browsing some fancy JS-driven blogs.