presenter is avoiding to mention that the guy who made Java script is Brendan Eich who was Mozilla CEO who was forced out of his position like the plague. He runs Brave Browser and Brave Search now
Hi everyone! This is sort of my synopsis of this talk. Please help me correct any mistakes I might have made. "How, in the future (now's present?), browsers will download web assembly instead of Javascript and run that. Web assembly is super fast for various reasons (mentioned at the end of this talk). This talk explains what web assembly is and how javascript, which is an imperative language, cannot be compiled into web assembly. However, its modules that you use in your code (like react's core code) CAN be converted to web assembly because they're written in the languages that can be compiled into web assembly (like C)."
Maybe I'm confused about WebAssembly. I ask because in the comments for this video I see people asking when will JS will be replaced by WebAssembly (as if programmers will be developing code in WebAssembly) and further more people speculating that JS won't likely be replaced completely by WebAssembly for another X years(?) so their NodeJS, Angular and JS skills are safe for now? Huh? I thought I understood from this talk that developers will still be writing their applications in high level languages (e.g., JS, plus others). It's just that these High Level Languages will get compiled into WebAssembly code that will be downloaded and run in the browser (after it gets translated into machine code by the browser engine). So with that context in mind I don't understand all of this discussion/speculation about WebAssembly replacing JS and obsoleting other high level software tools (e.g., Nodejs, Angular). It's not a competing technology to high level software dev tools...it's complimentary, right? Am I missing something?
its complimentary yes. WebAssembly allows us to use code from languages that can be compiled to wasm, e.g. rust, c++, etc. JS is designed for the web, but c++ for e.g. is able to access low level apis that js can't, and that opens up a lot of possibilities. One example that google gives is their "sqoosh" app, which is able to do amazing image compression using some c++ libraries that existed for decades. Compression on browsers isn't nearly as good.
This was very clear in explaining webassembly compared to a lot of other videos in TH-cam. I am learning javascript, nodejs, and angular... will these technologies be abandoned in next 5+ years?
Nah, think of WebAssembly as the superfast alien-dude with lots of arms, hidden under the table at the post office in Men in Black II. Javascript is more like Agent K, and Node is the beat-boxing alien.
Javascript is still one of the best interpreted languages out there. WASM is meant to integrate JS with static typed, compiled languages without garbage collectors, such as C, C++ and Rust.
Excellent presentation. Manual memory management and numbers only.... I think there is some ground to cover before this is getting widely used. And I can't help to wonder if wasm is that important... I mean if it is only number crunching, how much of that would you like to run on the client anyway?
why do we need move efficient js in the first place.. like we can make all kind of CRUD operations now with node and other languages whats more do we need js for, besides graphics orientaed work ??
Typescript compiles to JS so no atm.... And theoretically yes and no... Since ts is technically type safe language it probably could compile into WebAssembly but that said there is inherent flaw in that logic. Typescript is superset of JS, i.e any js file work as is in a ts file. So typesafety is optional, so unless you turn on strict typesafety on ts file you probably can't compile ts file into WebAssembly
+Jishnu Viswanath Does typescript have a JIT, if not let's say Microsoft builds a JIT for Typescript then it would not require intermediate JS conversion and would directly interact with the processor. I am talking about desktop applications, not website if you were wondering.
Sort of. As I understand it, TypeScript is faster because it transpiles to JavaScript where the types don't change. Allowing the engine to do a lot more optimisation and never have to de-optimise.
This is a comparison of interpreted languages vs binary code. Waste of time, if you're here to learn details specific to web assembly. Such as how stack/heap/program memory is allocated, is there GC multi threading. Is there separation similar to kernel /user space
20:30 The most hardcore LLVM fan in the audience :D
Lol
yep, we heard him XD cheers back for you too XD
Heard that too xD
FUCK YEAH
Fantastic presentation. Thank you. I love these high level overviews. Most of us want to "get to coding" but without context it's only zombie coding.
zombie code i love the word. lol.
Awesome speaker with great illustrations. Clear, instructive and dynamic talk on this interesting topic.
Bravo! Excellent, crystal clear explanation of a difficult topic! (Particularly for non-programmers, and more "visually-oriented" individuals.) TY!
She's really good.
Wow, she ate this talk up. Very clear, very precise. Danke!
awesome talk, awesome illustration. AWESOME! ;D
This is incredibly informative. Thank you
She is an absolutely brilliant speaker.
Absolutely brilliant talk. THANK YOU !
Such an excellent presentation - and a very talented speaker.
A great presentation. Learned a lot. Thank you :)
She's very good at explaining.
This is such a good presentation. Thoroughly enjoyed.
presenter is avoiding to mention that the guy who made Java script is Brendan Eich who was Mozilla CEO who was forced out of his position like the plague. He runs Brave Browser and Brave Search now
fav speaker
THE Conferencist.
Hi everyone! This is sort of my synopsis of this talk. Please help me correct any mistakes I might have made.
"How, in the future (now's present?), browsers will download web assembly instead of Javascript and run that. Web assembly is super fast for various reasons (mentioned at the end of this talk). This talk explains what web assembly is and how javascript, which is an imperative language, cannot be compiled into web assembly. However, its modules that you use in your code (like react's core code) CAN be converted to web assembly because they're written in the languages that can be compiled into web assembly (like C)."
Great talk, loved it!
Maybe I'm confused about WebAssembly. I ask because in the comments for this video I see people asking when will JS will be replaced by WebAssembly (as if programmers will be developing code in WebAssembly) and further more people speculating that JS won't likely be replaced completely by
WebAssembly for another X years(?) so their NodeJS, Angular and JS skills are safe for now? Huh?
I thought I understood from this talk that developers will still be writing their applications in high level languages (e.g., JS, plus others). It's just that these High Level Languages will get compiled into WebAssembly code that will be downloaded and run in the browser (after it gets translated into machine code by the browser engine). So with that context in mind I don't understand all of this discussion/speculation about WebAssembly replacing JS and obsoleting other high level software tools (e.g., Nodejs, Angular). It's not a competing technology to high level software dev tools...it's complimentary, right?
Am I missing something?
its complimentary yes. WebAssembly allows us to use code from languages that can be compiled to wasm, e.g. rust, c++, etc. JS is designed for the web, but c++ for e.g. is able to access low level apis that js can't, and that opens up a lot of possibilities.
One example that google gives is their "sqoosh" app, which is able to do amazing image compression using some c++ libraries that existed for decades. Compression on browsers isn't nearly as good.
Really good presentation !
after watching this.
just realized it will take longer to understand/'get' webassembly that I thought ...
WOW!! This is a really cool presentation.
What a brilliant presentation.
wow, i learned a lot from this talk
Fantastic talk. I get it now!
heptapods at 7:14! ! It is like the scene of Arrival.
Extremely excellent presentation.
Amazing
She is amazing
This was very clear in explaining webassembly compared to a lot of other videos in TH-cam.
I am learning javascript, nodejs, and angular... will these technologies be abandoned in next 5+ years?
Nah, think of WebAssembly as the superfast alien-dude with lots of arms, hidden under the table at the post office in Men in Black II. Javascript is more like Agent K, and Node is the beat-boxing alien.
Javascript is still one of the best interpreted languages out there. WASM is meant to integrate JS with static typed, compiled languages without garbage collectors, such as C, C++ and Rust.
Brilliant talk. Thank you. I just saw another fantastic talk on WebAssembly by Dan Callahan (also from Mozilla). Are all Mozilla folks this good? :p
You really made my day with that video thanks a lot
When will wasm be able to manipulate the dom?
I don't think that would give any significant performance improvements, but I could be wrong.
@@orlovsskibet true it wont gain any performance upper hand, but some people hate js to the core lol... (i am typescript fan)
@@orlovsskibet it could, because you may be doing something in WASM and you'd not need to go back and forth with the JS runtime in order to do stuff.
great stuff!
Excellent intro to web assembly.
What a good introduction!
This is amazing
Excellent presentation.
Manual memory management and numbers only.... I think there is some ground to cover before this is getting widely used. And I can't help to wonder if wasm is that important... I mean if it is only number crunching, how much of that would you like to run on the client anyway?
WebGL
Thanks. You delivered great, but I am little dumb to fully understand this stuff. Still wrapping my head around :-(
7:16 Arrival movie reference
why do we need move efficient js in the first place.. like we can make all kind of CRUD operations now with node and other languages whats more do we need js for, besides graphics orientaed work ??
Yep, why so we need more than 640k anyways LOL
So Typescript faster than Javascript because it can optimize everything, in the beginning, itself?
Typescript compiles to JS so no atm.... And theoretically yes and no... Since ts is technically type safe language it probably could compile into WebAssembly but that said there is inherent flaw in that logic. Typescript is superset of JS, i.e any js file work as is in a ts file. So typesafety is optional, so unless you turn on strict typesafety on ts file you probably can't compile ts file into WebAssembly
+Jishnu Viswanath Does typescript have a JIT, if not let's say Microsoft builds a JIT for Typescript then it would not require intermediate JS conversion and would directly interact with the processor. I am talking about desktop applications, not website if you were wondering.
vignesh sivakumar why does typescript need jit? It compiles into js and checks typesafety first
Sort of. As I understand it, TypeScript is faster because it transpiles to JavaScript where the types don't change. Allowing the engine to do a lot more optimisation and never have to de-optimise.
Fall out Raider help us understand new technology :))
Web assembly : 15:34
This is a comparison of interpreted languages vs binary code. Waste of time, if you're here to learn details specific to web assembly. Such as how stack/heap/program memory is allocated, is there GC multi threading. Is there separation similar to kernel /user space