Sam Thorogood sur Dev.to écrit,
Why did I write this post? Emscripten is a wonderful tool, but it has a long history (for asm.js), and isn't perfect. I think it errs too much on the side of "magic", and many posts rave about how it's so easy to EM_ASM_ or use binding-fu, but this all comes at a cost, and can introduce huge amounts of inadvertent overhead—think copying huge memory buffers around because we're trying to make them immutable or easily exposed.
Every language that is being compiled to Web Assembly needs a runtime—whether it be Go, or Rust, or C/C++ as we have here. I don't believe that we'll ever really be able to directly import Web Assembly via ES2015 modules, at least not without changes on the JS side. But it behooves us to write the smallest one we possibly can.
Je pense que nous voyons tous le potentiel du wasm, mais pour beaucoup d’entre nous, beaucoup d’autres plates-formes qui sont maintenant capables de s’introduire sur le Web nous sont totalement étrangères et nous devons vraiment apprendre ces outils, améliorer l’expérience du développeur wasm. et imo offre des bibliothèques prédéfinies que les développeurs Web traditionnels peuvent utiliser.
About Me: Paul Kinlan
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.