InfoQ Homepage WebAssembly Content on InfoQ
Articles
RSS Feed-
WebAssembly at Sentry - Q&A with Armin Ronacher
Sentry sees great potential in WebAssembly and uses it internally in the context of its ingestion system. However, further usage is hampered by the limited capabilities of WebAssembly when debugging in production. While proposals exist to make the DWARF standard debugging format work with Wasm, more work and better tooling are necessary. InfoQ interviews Sentry's Armin Ronacher.
-
How to Use Encryption for Defense in Depth in Native and Browser Apps
Isaac Potoczny-Jones discusses the pros and cons of application-layer encryption. He covers the attack surface of application-layer encryption in the browser, how it is very different from native clients, and how WebCrypto helps.
-
Mono: from Xamarin to WebAssembly, Blazor, and .NET 5 - Q&A with Miguel de Icaza
Mono started as an open source .NET platform in 2001, being developed by Xamarin until 2011. Since the company’s acquisition by Microsoft in 2016, both Mono and .NET Core have been developed in parallel. In the light of the most recent releases, InfoQ interviewed Miguel de Icaza —the original author of the Mono project—to talk about the current state of Mono and its future in the .NET ecosystem.
-
Porting a Desktop Game Editor to the Browser with WebAssembly
Florian Rival, software engineer at Google and creator of the GDevelop game editor, discusses the lessons learnt from porting a native desktop game editor to the browser with WebAssembly. InfoQ interviewed Rival on the technical challenges encountered, the benefits derived from the port, and tips for developers thinking about porting desktop applications with WebAssembly.
-
WebAssembly and Blazor: A Decades Old Problem Solved
A framework, named Blazor because it runs in the browser and leverages a templating system or "view engine" called Razor, enables the scenario .NET developers almost gave up on. It doesn't just allow developers to build client-side code with C#, but also allows developers to run existing .NET Standard DLLs in the browser without a plugin. Here's the story of WebAssembly and Blazor.