I am never writing another line of Javascript. React is pure

There's no way to interact with the DOM with wasm.

Javascript is going to be around fucking forever.

>>59011179
That's what JS is for, faggot. Not full stack abominations.

>>59011179
The DOM needs to die

>>59011163
You need to try Dart.

>>59011163
The only issue with webasm is it essentially kills 'apps'. Now users will just download a proprietary binary with their browser for literally everything you'll just start your GUI desktop which opens a browser in full screen mode because Office, Calculator, games, photoshop ect ect will all be a downloaded binary interacting in the fully cancerous browser environment.

So in effect we are just multiplying cancer not ridding ourselves of it

>>59011413
Apps are gay.

t. App developer

>>59011413
javascript is already extremely minified and obfuscated so it's just as bad as being "compiled" at this point.

>>59011179
wasm will support DOM interaction eventually

https://github.com/WebAssembly/design/blob/master/GC.md

>>59011413
most javascript code are already "non-free" and barely readable due to minification, WASM won't make a huge difference.

So does this mean I can write my web applications in C?

>>59011559
wasm performance is the difference maker, meaning you can create all kinds of things to run in browser you never could before like a game with proper latency

>>59011572
yeah, you will probably need some library loaded in your compiler that allow you to manipulate the DOM content

>he doesn't write his cli progs in node
kek

>>59011572
Yes
http://webassembly.org/docs/c-and-c++/

>>59011163
wasm isn't fundamentally going to change anything. It just means that you'll be able to write frontend apps in languages other than JS. But you can already do that since many languages out there have JS transpilers. Sure performance is kinda bad (but not that bad because V8 is actually pretty good).

I don't understand what you hate. Frontend development is always going to be a pain in the ass. It's not like having the ability to write it in different languages will make things fundamentally easier - it won't.
GUI development historically has always been the most tedious and shitty domain of software development.

>>59011572
It also means you can write web apps in scheme/lisp too that can compile directly to bytecode and run natively in the java browser virtual machine. tfw people start hiring common lisp web app "full stack developers"

File: 1484257683782.jpg (27KB, 589x386px) Image search: [Google]

27KB, 589x386px

when will modern browsers finally support wasm natively? I think chrome now has it as "experimental" in plugins config but not enabled as default yet

>>59011699
Roadmap is here http://webassembly.org/roadmap/

By end of this year it's expected all browsers will have it on by default