4 ms·

I'm waiting for WebAssembly to receive stronger toolings and lib until a radically new way to program the frontend appears. Ah, and I will relish to see the end

I'm waiting for WebAssembly to receive stronger toolings and lib until a radically new way to program the frontend appears. Ah, and I will relish to see the end of the Javascript dominance of the browser. I can say that again. I would love to see Javascript kicked away of the browser and replaced with something less asinine that doesn't require transpilation (Babel, etc), nor a slow kludgy hack to have a weak type safety net (TypeScript). Meanwhile, i'm sick of the current state of the art for the web frontend. It is currently so convoluted and unprofessional, that programming a Windows desktop application using the ancient, verbose Win32 API looks like heaven, compared to it. In any case, if you need an alternative, Svelte looks good.

mars4rp 9y ago
the problem is not JS, problem is people are not using the latest version of browsers. if you have to still support IE because your clients still use it, I don't see how WebAssembly can help!
jbreckmckye 9y ago
Expect to keep waiting. WebAssembler does not interact with the DOM and probably never will do. It is being developed as an replacement to NaCl, not V8. Page scripting will still be done in JS for several years.
- flavio81 9y ago
  >WebAssembler does not interact with the DOM and probably never will do. Because it doesn't really need to. You can already bridge this gap by using javascript as a bridge or "glue" between WebAssembly and the DOM. Example: https://github.com/mbasso/asm-dom https://github.com/mbasso/asm-dom > Page scripting will still be done in JS for several years. There are people who thought that corporate web pages would be done in Flash (& Actionscript) for several years.