Live data from Hacker News

Assembling WebAssembly

webkit.org

71–80 of 91 posts

Re: Assembling WebAssembly

#71

I hope wasm becomes the first class citizen and JavaScript becomes just one out of many languages that compiles to it. JavaScript is not bad at the high level, but at the low level it has been hell for engineers to implement a fast VM. A wasm VM is way easier to implement than a JavaScript VM.

Has it?

The fastest VMs on the planet are JS VMs right now.

Re: Assembling WebAssembly

#72
post #69

Earlier quoted context omitted.

HTML/CSS/JS has some huge advantages from the user perspective. When a designer has made some questionable choices, all it takes is a user stylesheet or a quick tour to the devtools to fix the font size and contrast ratio. The whole world of extensions that improve existing websites with additional buttons etc. is only possible because the page structure is exposed in the DOM. If Reddit were only WASM rendering on a…

Also, nobody wants to pay a C++ dev for doing a JS devs work, haha

you can still code in js or any other language.

Re: Assembling WebAssembly

#74
post #58

Earlier quoted context omitted.

Give me qt in the browser, the rest are details.

boom, qt, gtk, even xlib (or a win32 clone) would be better than html/css/js bullshit

How do you easily skin xlib or win32? (I think that Qt and Gtk support stylesheets)

Re: Assembling WebAssembly

#75
post #16

Man, we are bringing a giant load of complexity into the browser with this. As I understand it, what we get in return is a 2x speed increase. I wonder if its worth it.

We are potentially removing the complexity at all ends. Right now the chain is: Developer writes code in something like Typescript that then is translated to Javascript and then is downloaded by the browser (huge downloads compared to binary code). The browser then needs to parse that huge amount of javascript code to compile it into a bytecode that can then be JIT executed or interpreted. With webassembly it would b…

That's assuming the old ways are deprecated and removed.

There's countries in the world that still use IE6, and that's comparatively an easier transition :)

Re: Assembling WebAssembly

#76
post #71

I hope wasm becomes the first class citizen and JavaScript becomes just one out of many languages that compiles to it. JavaScript is not bad at the high level, but at the low level it has been hell for engineers to implement a fast VM. A wasm VM is way easier to implement than a JavaScript VM.

Has it? The fastest VMs on the planet are JS VMs right now.

Well, there's a smart fellow called Mike Pall who would like to race Lua against JavaScript for you. Plus, the very best VMs are Java.

Re: Assembling WebAssembly

#77
post #74

Earlier quoted context omitted.

boom, qt, gtk, even xlib (or a win32 clone) would be better than html/css/js bullshit

How do you easily skin xlib or win32? (I think that Qt and Gtk support stylesheets)

I think you could still use stylesheets, just not for the good defaults.

Re: Assembling WebAssembly

#78

Earlier quoted context omitted.

HTML/CSS/JS has some huge advantages from the user perspective. When a designer has made some questionable choices, all it takes is a user stylesheet or a quick tour to the devtools to fix the font size and contrast ratio. The whole world of extensions that improve existing websites with additional buttons etc. is only possible because the page structure is exposed in the DOM. If Reddit were only WASM rendering on a…

reddit would probably have an opensource rendering layer or third party uis that use it's api. wasm will be the new android without the need to install apps.

That's what they said about HTML 5, too.

Re: Assembling WebAssembly

#79
post #46

I hope wasm becomes the first class citizen and JavaScript becomes just one out of many languages that compiles to it. JavaScript is not bad at the high level, but at the low level it has been hell for engineers to implement a fast VM. A wasm VM is way easier to implement than a JavaScript VM.

I do like the upside, but coupled with DRM support, it's going to be used to obfuscate, hide and control things. I'm expecting a much less open web coming.

Well, while true, today many things are being hidden from browsers by doing them server-side.
Post reply on HN