Will Emscripten/Asm.js kill Web-Development as we know it?

Re:Will Emscripten/Asm.js kill Web-Development as we know it? by ebbv on Thursday March 28, 2013 @09:11AM (#5454544)

You can't "do away with the DOM altogether". You need to have some method of interacting with the browser; location, AJAX requests, cookies, etc.

Porting a GUI toolkit only relieves your need to deal with CSS, it does not alleviate you of all need for the DOM.

[ Parent | on HN ]

Re:Will Emscripten/Asm.js kill Web-Development as we know it? by swombat on Thursday March 28, 2013 @09:12AM (#5454549)

You're splitting hairs. In practice, if all you're dealing with from the DOM is one canvas element and a URL that's static, you've pretty much "done away" with the DOM.

[ Parent | on HN ]

Re:Will Emscripten/Asm.js kill Web-Development as we know it? by ebbv on Thursday March 28, 2013 @09:16AM (#5454571)

That's not true at all. You need some way of interacting with a back end (as well as the browser.) Whether that's via forms or AJAX requests, you need more from the DOM. The DOM is not just a GUI toolkit.

I am not splitting hairs, you are glossing over serious limitations to this approach.

[ Parent | on HN ]