4 ms·

Off the top of my head: - Games - Emulator cores - Crypto - Compression - Software graphics - Audio processing - Computer vision - Phys

Off the top of my head: - Games - Emulator cores - Crypto - Compression - Software graphics - Audio processing - Computer vision - Physics engines - Other heavy math/matrix/constraint solvers - In-memory databases Besides games, all of these are library uses, and tend to have fixed structure definitions and often even fixed memory buffers to work with (crypto in particular). The developer is still writing the main application in JavaScript (or whatever other dynamic/GC'd language you wish to compile into JS) and gets the full speed and memory footprint benefit of pulling libraries such as these as opposed to seeking pure JS versions.

tannhaeuser 10y ago
- DRM
- AgentME 10y ago
  If it lives in the relatively restricted sandbox of the browser, then that's not any scarier than DRM written in Javascript in a browser.
  - pdkl95 10y ago
    Have fun writing a new adblocker for each page. Yes, debugging/decompiling is possible, but that is far scarier than the the current situation. When it's possible to ignore the DOM by uploading your own renderer (e.g. custom freetype/etc compiled to webasm), it's possible to prevent adblocking based on HTML/CSS selectors.
    - AgentME 10y ago
      WebAssembly doesn't necessarily mean "do everything in canvases".
      - pdkl95 10y ago
        Of course. Similarly, I doubt Adobe intend for Flash to replace entire websites with over-animated single page apps with terrible usability, but that's how many websites used Flash In the late 90s. Yes, well-designed sites will use WebAssembly in other more reasonable ways. Entirely separate from that are the websites that try to disable the right-click context menu to "protect" images, and the businesses that are watching there revenue disappear with the rise in adblocking. Some businesses will - often foolishly - use all available means to "protect their content", so that's how they will use WebAssembly.
    - tannhaeuser 10y ago
      This exactly. WebAss, being suspiciously implemented by major browser vendors in a fellow swoop, is simply an assault on the principles of the open web. As usual, cheered at by technical brilliant, but otherwise clueless nerds getting lost in arguments about the merits of their favourite programming language vs JavaScript, but incapable of seeing the bigger picture. I wish Apple could kill it.
      - greglindahl 10y ago
        You could make your point without the sarcasm and name-calling. Presumably you'll be authoring a "NoAss" add-on, following along in the "NoScript" tradition.
        tannhaeuser 10y ago
        Brilliant. More fecalia-themed names: AssAssassin SafeAss MyAss OpenAss
        tannhaeuser 10y ago
        You can also combine it: SafeMyAss OpenMyAss

tannhaeuser 10y ago

- DRM

AgentME 10y ago
If it lives in the relatively restricted sandbox of the browser, then that's not any scarier than DRM written in Javascript in a browser.
- pdkl95 10y ago
  Have fun writing a new adblocker for each page. Yes, debugging/decompiling is possible, but that is far scarier than the the current situation. When it's possible to ignore the DOM by uploading your own renderer (e.g. custom freetype/etc compiled to webasm), it's possible to prevent adblocking based on HTML/CSS selectors.
  - AgentME 10y ago
    WebAssembly doesn't necessarily mean "do everything in canvases".
    - pdkl95 10y ago
      Of course. Similarly, I doubt Adobe intend for Flash to replace entire websites with over-animated single page apps with terrible usability, but that's how many websites used Flash In the late 90s. Yes, well-designed sites will use WebAssembly in other more reasonable ways. Entirely separate from that are the websites that try to disable the right-click context menu to "protect" images, and the businesses that are watching there revenue disappear with the rise in adblocking. Some businesses will - often foolishly - use all available means to "protect their content", so that's how they will use WebAssembly.
  - tannhaeuser 10y ago
    This exactly. WebAss, being suspiciously implemented by major browser vendors in a fellow swoop, is simply an assault on the principles of the open web. As usual, cheered at by technical brilliant, but otherwise clueless nerds getting lost in arguments about the merits of their favourite programming language vs JavaScript, but incapable of seeing the bigger picture. I wish Apple could kill it.
    - greglindahl 10y ago
      You could make your point without the sarcasm and name-calling. Presumably you'll be authoring a "NoAss" add-on, following along in the "NoScript" tradition.
      - tannhaeuser 10y ago
        Brilliant. More fecalia-themed names: AssAssassin SafeAss MyAss OpenAss
        tannhaeuser 10y ago
        You can also combine it: SafeMyAss OpenMyAss