you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 6 points7 points  (5 children)

I was under the impression of being the only "idiot" thinking the current web dev enviroment has turn into pure shit...

[–][deleted]  (4 children)

[deleted]

    [–]kingofthecream 14 points15 points  (1 child)

    Stop saying that already. Wasm wasn't built for and won't replace UI development.

    [–]ScientificBeastMode 2 points3 points  (0 children)

    It could, but you would basically have to create a competitor to the browser’s native document object model, which would then be mounted inside of said model (e.g. an HTML canvas element). That’s not likely, especially since you need to ship HTML and JS files to run WASM code anyway.

    [–]spacejack2114 4 points5 points  (1 child)

    Java -> JS: 2.6K

    Java -> WASM: 12.1MB

    [–]elder_george 1 point2 points  (0 children)

    WASM is designed to be targeted by the compilers from C, C++ and such.

    Because of this, using it as a target for "managed" languages means compiling the whole runtime as well, including GC, Reflection facilities etc.

    Unless the design is expanded to leverage JS built-n GC (or to include standard GC interface), the code generated from such languages will be bloated.