-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e86689e
commit d794a56
Showing
1 changed file
with
33 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| --- | ||
| layout: post | ||
| title: ! "Issue #81" | ||
| author: ceberhardt | ||
| --- | ||
|
|
||
| ### [SwiftWasm](https://swiftwasm.org/) | ||
|
|
||
| <small>SWIFTWASM.ORG</small> | ||
|
|
||
| Big news for Swift fans (you should be a fan, it's a great language!), there has been some significant progress made towards bringing Swift to WebAssembly. This webpage provides an online demo, and a link to the team's pull request against Apple's Swift repo. | ||
|
|
||
| ### [1Password uses WebAssembly](https://blog.1password.com/1password-x-may-2019-update/) | ||
|
|
||
| <small>1PASSWORD.COM</small> | ||
|
|
||
| I always love hearing about where WebAssembly has found its way into production code - currently this doesn't happen too often as the tooling for wasm is still very much in active development. In this blog post the 1Password team indicate a significant performance increase due to their move to WebAssembly for parts of their codebase. | ||
|
|
||
| ### [How to build WebAssembly C# Apps with the Mono AOT and Windows Subsystem for Linux](https://platform.uno/how-to-build-webassembly-c-apps-with-the-mono-aot-and-windows-subsystem-for-linux/) | ||
|
|
||
| <small>PLATFORM.UNO</small> | ||
|
|
||
| Mono, the open source .NET runtime which is used in both Blazor and Uno, currently supports WebAssembly via an interpreted mode. To achieve this the .NET CLR itself is compiled to wasm and DLLs interpreted at runtime. Clearly this has some significant size and performance limitations. This blog post explores the experimental Ahead Of Time (AOT) compilation mode that will compile DLLs directly to wasm. | ||
|
|
||
| ### [V8 release v7.5 - introduces WebAssembly implicit caching](https://v8.dev/blog/v8-release-75) | ||
|
|
||
| <small>V8.DEV</small> | ||
|
|
||
| WebAssembly is going to keep getting faster ... this post from the Chrome team introduces wasm module caching. | ||
|
|
||
| ### And Finally ... | ||
|
|
||
| A few of us have been having fun creating [old-school demos in hand-coded WebAssembly](https://twitter.com/ColinEberhardt/status/1128701985757253632) - why not join the fun? Aaron's latest creation goes a [step further combining WebAssembly and WASI](https://twitter.com/torch2424/status/1129089108322578432). |