3 ms·

Meh, very few apps are cpu constrained. For vast majority targeting html5/javascript and it's mindboggingly huge installed base is a bigger win.

• leon_ 15y ago
  > 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.
• cageface 15y ago
  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.
  • ootachi 15y ago
    You assume wrong. Modern tracing or type-inferring JITs are heavily optimized for the kinds of tight loops you see in image processing.
    • cageface 15y ago
      All the heavy lifting in apps like that is done in SIMD.
      • ootachi 15y ago
        Which doesn't require NaCl. https://bugzilla.mozilla.org/show_bug.cgi?id=644389 https://bugzilla.mozilla.org/show_bug.cgi?id=644389
• nitrogen 15y ago
  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.