Speed, Speed, Speed: JavaScript vs C++ vs WebAssembly - Franziska Hinkelmann, Google

In Node.js, we can use WebAssembly modules and native C++ addons. If your app has performance critical parts, should you stay in JavaScript? Or write a native C++ addon? Or use WebAssembly? We’ll look at how these options compare performance wise and which one is best for different workloads. So the next time you need to optimize for speed, you know your options.

[@BenderdickCumbersnatch]

Just use TypeScript and AssemblyScript (a specialized version of TypeScript) and you can make WASM entirely in a TypeScript-like language. This gives you safe, type-based javascript and WebAssembly without having to learn other languages. They acknowledge that it won't be as fast as optimal WebAssembly from Rust, but it's good enough for most things.

[@fabianmarcus]

Sehr geil erklärt. Vielen Dank!

[@leors7578]

pretty good concise talk

[@smilingx4-189]

Good talk, I love benchmarks

[@IARRCSim]

yeah. I wish there were a few other algorithms tested, though. Benchmarks for 3 or 4 algorithms and ran with Chrome, Firefox, Edge would be a lot better. It would be nice to know if any of them have much different results.

[@Androide7461]

What I don't quite get is that, when you compared JavaScript to C++ to WebAssembly at 24:07, isn't there a speed difference in WebAssembly between "c++ - webassembly", "rust - webassembly" and "c - webassembly"?

[@avimehenwal]

webassembly is like an IR (Intermediate representation) standard ready to be executed in browser. No matter which source language you use like C/ C++ or Rust, they all will get compiled to almost similar wasm binary code. Therefore, I think "c++ - webassembly", "rust - webassembly" and "c - webassembly" should all product similar wasm binary and hence similar performance results.
Hope it helps! Cheers and Peace

[@nothingisreal6345]

The thing you should consider: optimizing the performance of JavaScript has maybe saved as much energy as replacing refrigerators from A+ to A++ energy rating.

[@someonesomewhere1879]

Very good talk. Great for understanding the basics of JS / WASM

[@IARRCSim]

Great performance comparison too.

[@trietti97]

Would you like to give me the scientific paper including these results?
Thank you.

[@ridhadepot1301]

Comparing C++ with Javascript is like comparing :
Potaetos with tomatoes

[@railbatyrshin7349]

two hundred first bleat'!

[@Ihavetoreturnsomevideotapes]

I thought he was dude