<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alexandre Morgaut on Medium]]></title>
        <description><![CDATA[Stories by Alexandre Morgaut on Medium]]></description>
        <link>https://medium.com/@amorgaut?source=rss-1dd97108b7fa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*dLQytGbIn-N6Bupw.png</url>
            <title>Stories by Alexandre Morgaut on Medium</title>
            <link>https://medium.com/@amorgaut?source=rss-1dd97108b7fa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:29:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amorgaut/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Web Assembly & the Future of JavaScript]]></title>
            <link>https://medium.com/@amorgaut/web-assembly-the-future-of-javascript-be0e925c096e?source=rss-1dd97108b7fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/be0e925c096e</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[rust]]></category>
            <category><![CDATA[webassembly]]></category>
            <dc:creator><![CDATA[Alexandre Morgaut]]></dc:creator>
            <pubDate>Sat, 25 Mar 2017 17:23:07 GMT</pubDate>
            <atom:updated>2025-08-16T13:32:47.566Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>There was an interresting article on Sitepoint called: <a href="https://www.sitepoint.com/life-after-js-learning-2nd-language/"><strong>Life after JavaScript: The Benefits of Learning a 2nd Language</strong></a> which pointed out a growing question concerning the rise of <a href="http://webassembly.org/"><strong>Web Assembly</strong></a>:</p><p><strong>What will become JavaScript once it will be possible to write faster Web Applications using more low level languages ?</strong> (and what about the future of JavaScript developers?)</p><p>The article author asked his readers to which second language we, JavaScript developers, would be more inclined to turn to. That’s an occasion to start writing full blog posts, so let’s go…</p><p>To start, let’s consider at least 3 points that, at minimum, extends JavaScript lifetime.</p><p>While <a href="https://en.wikipedia.org/wiki/Web_IDL"><strong>Web IDL</strong></a>(Interface Definition Language), used to standardise Web APIs, was first designed to be language agnostic (with Java, VB, &amp; JavaScript implementations), its <a href="https://www.w3.org/TR/WebIDL-1/"><strong>second edition</strong></a> and then the <a href="https://webidl.spec.whatwg.org/"><strong>WHATWG living standard version</strong></a>, became much more JavaScript dependent with a full <a href="https://webidl.spec.whatwg.org/#javascript-binding">JavaScript Binding section</a>. As of today, all Web API working group members think usage in JavaScript perspectives. For other languages to fully take over JavaScript, it will probably take time for them to:</p><ul><li>comply with Web IDL second edition requirements (natively or via libs)</li><li>wait for Dedicated Binding sections in Web IDL second edition</li><li>or wait for a Web IDL third edition.</li></ul><p><em>Update (2025): What we are waiting for actually, is a future Web assembly Binding section </em><a href="https://www.w3.org/2018/12/games-workshop/slides/08-web-idl-bindings.pdf"><em>which was mentionned in 2019</em></a><em>. This proposal moved to a Web Assembly </em><a href="https://github.com/WebAssembly/interface-types/blob/main/proposals/interface-types/Explainer.md"><em>interface-types</em></a><em> proposal which is still currently inactive.</em></p><p>Web Assembly engines relies on the <strong>JavaScript Virtual Machine</strong>. As Brendan Eich explained, it is too much complicated to have multiple virtual machines in a browser, as it relies on many binding, security and accessibility features (for the less). So any additional language engine is first imagined as be integrated via the JavaScript one. Google tried with its dart language, and Microsoft with its TypeScript language, but they both finally were externalized. This makes JavaScript support stay for a moment and let other languages come only either through transpilation step (like TypeScript), or a compilation to Web Assembly. At worst, the JavaScript language evolution may slow down or stop (some may prefer to say it will be stabilised). But do not forget that JavaScript is still also used on other platforms than Browsers so there will mostly be still people onboard for its evolution…</p><p>A large part of Web performance issues happen when interacting with the rendering engine. Websites and Web Applications <a href="https://www.w3.org/WAI/"><strong>Accessibility</strong></a> rely on HTML DOM elements &amp; attributes (ex: <a href="https://www.w3.org/WAI/intro/aria">ARIA</a>) and many institutions or local laws asSection 503 in US or RGAA in France, rely on application of such DOM related rules.</p><p>Canvas rendering is already often used from JavaScript, either in 2D or 3D WebGL contexts for Web editions of important application. It is already a big issue on that point, so I let you imagine with Web Assembly if not using the DOM (which currently rely on JavaScript calls). In native development for desktop &amp; mobile application, accessibility is provided by the main frameworks via the native UI components and via dedicated APIs (ex. .NET <a href="https://learn.microsoft.com/en-us/windows/win32/winauto/entry-uiauto-win32">UI Automation API</a>). So while Web Assembly programs use the DOM for rendering, then performances will be much more comparable to the JavaScript ones.</p><p><em>Note (2025): As of today, thanks to Web Assembly, heavy desktop applications such as </em><a href="https://web.autocad.com/"><em>Autocad</em></a><em> or </em><a href="https://www.figma.com/fr-fr/web-design/"><em>Figma</em></a><em> have been ported to the Web, but using Canvas for the rendering. It might be tolerable in some cases but alternative DOM rendering might be mandatory for main services.</em></p><p>Then, at least in first place, Web Assembly mostly allows to quickly port some business desktop applications to the Web or to write very native comparable fast modules <strong>for time expensive or sensible computations</strong> like:</p><ul><li>Video &amp; audio codecs,</li><li>Game animations,</li><li>Custom compression algorithms,</li><li>Potential <a href="https://www.w3.org/TR/encrypted-media/">EME</a> DRM modules (Cisco? Verimatrix? Nagra? …),</li><li>Some security encryption cyphers…</li></ul><p>Many things, for which we had to wait for browser vendor implementation, may come more easily as “wasm” modules for Web Applications.</p><p>At a higher level, we may imagine some wasm writen frameworks for JavaScript Developers, but I’m not sure the gain will be that big.</p><p><em>UPDATE (2025): Nowadays some Web developer tools which initially were developped in JavaScript start to be written in other languages like Rust (</em><a href="https://rolldown.rs/"><em>Rolldown</em></a><em> for </em><a href="https://vite.dev/guide/rolldown"><em>Vite</em></a>, <a href="https://oxc.rs/">OxLint</a><em>) or Go (esbuild) and built in wasm (Web Assembly) to run from node.js</em></p><p>JavaScript developer roles will be less focus on writing some core level optimisations, and more focused on high level feature integrations. We may fear it may needs less competences but my guess is probably that it will mostly make them focus on the real application business values.</p><p>All that said, some Web developers may still want to get back to more core features development, and Brendan Eich (again) explained also that because of the dynamic nature of JavaScript, he did not see possible to compile it in Web Assembly any time soon, which means that such limitation probably applies to other loosely typed / interpreted languages (PHP? Python? Ruby? …).</p><p>This will probably limit the number of people starting to use a language that compiles in Web Assembly, but for the more motivated ones which language should they start to look at?</p><p>Let’s bet then on 4 languages currently sponsored by our main browser vendors that are the most concerned by the future of Web Assembly:</p><ol><li>Rust, from Mozilla</li><li>Swift, from Apple</li><li>C#, from Microsoft</li><li>and Go (or Dart?), from Google</li></ol><p>As supported by Mozilla which provides the Web Assembly compiler (<a href="https://kripken.github.io/emscripten-site/docs/tools_reference/emcc.html">emcc</a>), I would not be surprised to see <a href="https://www.rust-lang.org/en-US/"><strong>Rust</strong></a> as one of the first emcc supported languages. And even more now that Browser more and more support multi-threading (V8 &amp; JSCore at least are thread-safe, web workers become more &amp; more supported &amp; SharedArrayBuffer is on the way), the concurrency optimisations of Rust could be interesting in this context. Note that Rust was used by Mozilla to write a whole new Browser called <a href="https://servo.org/"><strong>Servo</strong></a>, so it might also help to expose Web APIs to this language more quickly.</p><p>Developers I know that used <a href="https://swift.org/"><strong>Swift</strong></a> said its approaches move close to the JavaScript ones, and as being also the main language to code on Apple platforms (iPhone, iPad, Apple TV, upcoming Apple Car OS, …), it can be a very good bet. Apple wanting to push its home made language, Web Assembly support could be an option for them to work on and a good opportunity to attract Web developers to its ecosystem.</p><p>I’ve heard that Promises &amp; async/await have been a lot inspired from the <a href="https://en.wikipedia.org/wiki/C_Sharp_(programming_language)"><strong>C#</strong></a> implementation so I guess Async development in C# should be quite optimised with probably a nice collection of Async oriented libraries. It is also one of the nearest languages from C/C++ and as one of the core component of the .NET framework, it is probably what Microsoft will push for. It also was standardised at ECMA (as <a href="https://www.ecma-international.org/publications/standards/Ecma-334.htm">ECMA-334</a>) but the last publications are unfortunately always outdated compared to the last versions. For this language, implementation still comes before standardization ;-)</p><p>The fourth main Browser actor being Google (I’m not talking about browser usage competition), It would be fair to say, even if <a href="https://www.dartlang.org/"><strong>Dart</strong></a> may be more close to JS, that I would also have a look at its <a href="https://golang.org/"><strong>Go</strong></a> language that it may push as a Web Assembly provider. It could be an easier alternative for beginners, which was one of the target of JavaScript.</p><p>Still, we need to consider one thing. It is possible to write Web Backends in native code since a very long time, but aren’t most of them written in interpreted languages such as PHP, python, ruby, perl, and nowadays more and more in JavaScript?</p><p>So, I don’t care that much for the future of JavaScript in Web development. Web Assembly will mostly mean:</p><ul><li>a richer ecosystem of low level modules for Web developers</li><li>a door open a little wider to developers from other languages (It has already been open via the <a href="https://github.com/jashkenas/coffeescript/wiki/List-of-languages-that-compile-to-JS">large list of available transpilers</a>)</li></ul><p>In the end, we’ll probably have the time to wait the moment we’ll be able to compile JavaScript in Web Assembly without being that much frustrated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be0e925c096e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>