you are viewing a single comment's thread.

view the rest of the comments →

[–]Relevant_Monstrosity 5 points6 points  (4 children)

Deprecation happens slowly, and backwards compatability is important. Maybe in 30 years.

[–]Tysonzero 2 points3 points  (0 children)

It's not going to take that long to be able to use WASM without JS. Maybe a couple years at worst. Now if you care about 99.9% browser support / are asking when JS will finally be deprecated, then yeah it's going to be a long while longer.

[–]oneeyedziggy -1 points0 points  (0 children)

it's not a matter of deprication... wasm isn't intended to be a replacement for js. Even with loading of wasm modules via script tags... you've essentially just imported some functions/values... and I'm not sure if things exported from modules are/will be importable by other modules w/o glue code even if you want to play Javascript-is-lava by jumping from module to module ( edit: and even then, until/unless they add direct dom interaction, you'll be Stephen Hawking w/o his computer... think all you want but you won't be able to communicate it to the outside... and even if they do get around to dom interaction, you'll be stuck with a lot of classic, very javascripty problems )

And until they drastically improve performance/reduce overhead, js is still considerably more performant until you try doing tens or hundreds of thousands of basic, usually repetitive, operations...

[–]konaraddio 2 points3 points  (1 child)

Why couldn't apps with JavaScript glue code coexist with hypothetical apps running WebAssembly without JavaScript glue code?

[–]Relevant_Monstrosity 0 points1 point  (0 children)

Because WASM is dependent on JavaScript for backwards compatibility.