7 ms·

Javascript/WASM evolution: designed for applications running in a browser -> writing desktop and server applications -> writing an OS or kernel I can't put my

Javascript/WASM evolution: designed for applications running in a browser -> writing desktop and server applications -> writing an OS or kernel I can't put my finger on it, but somehow this looks familiar (hint: it starts with a "J", too)

timschmidt 3y ago
WASM manages the trick with a vastly simpler specification and runtime. Not much more than a compile target for other languages.
- meindnoch 3y ago
  Except it just got a garbage collector.
  - titzer 3y ago
    We're working to make sure that there will be an officially blessed subset (called a "profile") that will not require GC.
    - AndrewDucker 3y ago
      I'd be interested in knowing more about that. Is there a summary of current progress anywhere?
      - titzer 3y ago
        This is the repo for the "profiles" feature by which we will define standard subsets: https://github.com/webassembly/profiles https://github.com/webassembly/profiles
  - swsieber 3y ago
    It did? I thought that proposal was basically stuck; I haven't checked in a while, but I haven't heard of it moving forward either.
    - johncolanduoni 3y ago
      Chrome will be shipping it in the next version: https://chromestatus.com/feature/6062715726462976 https://chromestatus.com/feature/6062715726462976
  - davexunit 3y ago
    Which makes it an even better compilation target!
starlevel003 3y ago
Can't wait for the Wazelle processor extensions to drop.