I am using Go as my development language for last 2 years and I am always curious to write some frontend using Go. But it was no luck for a while until go 1.11.1 released with experimental WebAssembly port. So, I had my small experiments with it.
I developed two experimental applications: https://medium.com/@rajnikant12345/go-webassembly-my-experiment-6fc21d4ef4e7
Do you want to run your lovely Qt Quick app on the browsers? Before Qt 5.12, the only way is to use the Qt WebGL streaming plugin. It is, however, just a mirror of the UI and suffers from some problems which will be mentioned later. Starting with Qt 5.12, a new module emerges, the Qt for WebAssembly(QtWasm for short). Briefly speaking, it’s a trial to compile the Qt framework to webassembly, a new form of bytecode that can run on the browsers. This post will explan how to write your first QtWasm app in details, and try to provide solutions to some problems you will inevitably encounter.
Read the article: https://medium.com/@jimmychen009/qt-quick-on-the-browser-30d5349c11ec
When developing for the web, there have been plenty of times where I couldn’t bring my idea to fruition due to browser performance. Browsers do not run instructions directly like a compiled executable written in C. Browsers have to download, parse, interpret, and Just-In-Time (JIT) compile JavaScript (JS / ES6). I’ve built more than a handful of Cordova / Ionic, Electron, and Progressive Web Apps (PWA) to allow myself to have the portability and flexibility of the web, but I knew it was always at the sacrifice of performance; So the moment I heard the whispers of WebAssembly (Wasm), I knew I had to jump in on it.
Read the article: https://medium.com/@torch2424/webassembly-is-fast-a-real-world-benchmark-of-webassembly-vs-es6-d85a23f8e193
After many months of development, version 1.0 of WebAssembly (wasm for friends), is here.
WebAssembly https://webassembly.org/
Read the article: https://medium.com/@interlogica/webassembly-1-0-786e4c12e578
In my previous post, I talked about WebAssembly (WASM) and its potential through the eyes of a JavaScript web developer. (I recommend reading that post before this one)
After writing my post I was excited to use WASM in a real application I was developing at my internship at GDK Software. I was not developing applications with real heavy calculations so there wasn’t a proper use for WASM, but that did not slow me down in using this new technology.
Read the article: https://medium.com/@BartInTheField/c-map-compiled-to-webassembly-vs-javascript-map-39af1c950d6c
We started Wasmer with the goal of running standalone, platform-dependent applications on any platform or architecture so that developers can focus on what really matters: reaching a bigger market faster with less effort.
For that, we realized that WebAssembly is the ideal technology to leverage:
Read the article: https://medium.com/@syrusakbary/running-nginx-with-webassembly-6353c02c08ac
In this article, we will create a reusable grid component for Blazor called BlazorGrid. It will display the user data in a grid and supports client-side pagination.
Read the article: https://medium.com/swlh/how-to-create-a-reusable-grid-component-for-blazor-9de4b7a669d9
In this article, we will learn how to publish a reusable Blazor component to nuget gallery. We will use Visual Studio 2017 to build and create the nuget package.
Read the article: https://medium.com/swlh/how-to-publish-a-blazor-component-to-nuget-gallery-850d6d1dd37d
Rust is a wonderful language which aims to be a competitor of C++. The focus areas of rust are memory safety and high system performance. The curious case of rust is that it has no garbage collection, but claims to achieve memory safety through its enforcement of “lifetimes” for variables. Along with these features an interesting balance between imperative and functional programming style make rust quite appealing.
Read the article: https://medium.com/@joydeepubuntu/rust-for-the-react-developer-1937127efcac
This post compares GopherJS to Go 1.11 and its new experimental WebAssembly port, suggests how Web API binding libraries can evolve to support both compilers, and provides context on the history and the future possibilities of Go in the browser.
Read the article: https://medium.com/gopherjs/future-of-gopherjs-and-go-in-the-browser-cc1667468160