This article was first published on OntologyNetwork - Medium
Imagine you are a dApp developer and you have just launched a puzzle game dApp on a leading public blockchain platform after months of research and coding. Since its launch, the number of users has skyrocketed. Instead of becoming complacent, you began to think about what’s next:
What will become of this dApp?
Scenario 1: This puzzle game is super fun! The game has taken the world by storm since its launch, and is now on the most-popular dApp ranking! So you are thinking of bringing the dApp onto other top public blockchains to reach more users.
Scenario 2: User growth soon reached a plateau. So you are thinking of moving the dApp to other platforms to explore new opportunities.
You then realized that if the dApp can be instantly integrated into different platforms, it will enjoy long-term growth.
However, you need to use different programming languages to develop dApps on different public blockchains. If you have the same problem, then the Ontology Wasm is just the right thing for you.
What is Wasm?
Wasm is a binary instruction format initiated by Google, Microsoft, Mozilla, and Apple. It enables deployment on the web for client and server applications.
Wasm MVP standard is now supported by most mainstream browsers. Moreover, applications written in many other languages (C, C++, and Rust) can be compiled into Wasm byte code. An application ecosystem based on this greatly reduces the learning costs for developers.
Currently, EOS is one of the few public blockchains which support Wasm VM. Some are still under development. The Rust community by far offers the most comprehensive support for Wasm, as its compiler and the standard library can be used directly. Some other languages are also carrying out experimental projects on Wasm, such as Go, Python, and Java....
To keep reading, please go to the original article at:
OntologyNetwork - Medium