EVM or eWASM?

[Abiky]

I've seen somewhere that the Ethereum development team is planning to switch from EVM to eWASM. This is supposed to increase efficiency on the ETH blockchain, while making use of a tried-and-tested programming language for the web (WebAssembly). EOS is already using WebAssembly, and so far, it's been doing great. But switching to another virtual machine quickly on ETH could prove to be troublesome for smart contract developers. There's already an established ecosystem of dApps and tokens using the EVM. I doubt anyone would want to migrate their dApps into eWASM after all the hard work was done on the prior virtual machine.

Do you think it's a good idea for Ethereum to switch from EVM (using Solidity) to eWASM? Is it best to "leave it as is"? Please cast your vote on the poll above and feel free to express your opinion about it. Thanks.

[Lagduf]

Ethereum dev has very strong reasons about why they wanna use eWASM as a replacement for EVM. EVM is less compared with eWASM in Speed and Efficiency, Precompiles and Interoperability.

I think anyone will migrate their dapp into the eWASM when they were seeing if that was offering a lot of advantages.

Did you know that if eWASM is actively developed by engineers from the major companies like google and apple? It's not a big problem if ethereum wanna move to the eWASM as long as it gives a lot of benefits.

[Abiky]

Ethereum dev has very strong reasons about why they wanna use eWASM as a replacement for EVM. EVM is less compared with eWASM in Speed and Efficiency, Precompiles and Interoperability.

I think anyone will migrate their dapp into the eWASM when they were seeing if that was offering a lot of advantages.

Did you know that if eWASM is actively developed by engineers from the major companies like google and apple? It's not a big problem if ethereum wanna move to the eWASM as long as it gives a lot of benefits.

Yes, I'm aware. The WebAssembly programming language proves to be extremely efficient for web-based applications. It's been supported by Google and some other prominent companies for as long as I remember. On the other hand, the EVM's programming language (Solidity) is relatively new to the space. There are a lot of bugs and insecurities which make Solidity inferior to the already-established WebAssembly programming language. eWASM will surely provide greater benefits than the existing EVM. But it'll take some time before developers decide to migrate their dApps to the new virtual machine. After all, it's not easy to switch from an established infrastructure to a completely new one.

By combining the benefits of eWASM and PoS, Ethereum could enjoy greater scalability like never before. Transactions and smart contract computations will be a lot more cheaper than what they are right now. I think that if the Ethereum dev team does this, the project will be very close to scalable smart contract platforms like EOS and TRON. We'll have to see how everything unfolds with ETH right after the adoption of a wholly-new virtual machine for smart contracts. Just my opinion

[BintangBuleun]

I've seen somewhere that the Ethereum development team is planning to switch from EVM to eWASM. This is supposed to increase efficiency on the ETH blockchain, while making use of a tried-and-tested programming language for the web (WebAssembly). EOS is already using WebAssembly, and so far, it's been doing great. But switching to another virtual machine quickly on ETH could prove to be troublesome for smart contract developers. There's already an established ecosystem of dApps and tokens using the EVM. I doubt anyone would want to migrate their dApps into eWASM after all the hard work was done on the prior virtual machine.

Do you think it's a good idea for Ethereum to switch from EVM (using Solidity) to eWASM? Is it best to "leave it as is"? Please cast your vote on the poll above and feel free to express your opinion about it. Thanks.

I think AVM is already the best for Ethereum smart contracts. This is simpler to use. But what needs to be fixed is about the abnormal gas fees in each smart contract used. Solidity format that is too complicated to make fees is quite high when the transaction. For example the SmartFund token, this requires a high enough fee for the transaction. This token uses pragma solidity 0.4.23.

[leea-1334]

I do not know much about all these different languages but I actually think this time WASM is a good choice. It is now the direction for a lot of applications, even outside blockchain, which to me means that this is one language everyone can understand and get compatible with each other. It will not be the last move,,,

[Abiky]

I do not know much about all these different languages but I actually think this time WASM is a good choice. It is now the direction for a lot of applications, even outside blockchain, which to me means that this is one language everyone can understand and get compatible with each other. It will not be the last move,,,

Completely agree with you, mate. eWASM is much faster and efficient than the current EVM. Using a tried-and-tested programming language like WebAssembly could really make smart contracts on Ethereum much more reliable. The only issue with adopting a new virtual machine is the steep learning curve from existing Solidity developers into WebAssembly. Besides that, it'll be a troublesome process to migrate dApps and tokens from the EVM to eWASM. I'm sure that the ETH dev team will come up with a straightforward solution to "tackle" this issue.

But first things first. Before we talk about eWASM, ETH needs to become a full-fledged PoS cryptocurrency. After scalability issues are solved, the ETH dev team could decide to go all-in with eWASM. There have been talks about adopting ProgPoW before going to PoS and the likes. As long as ETH takes the "safest route" in terms of development and innovation, nothing should go wrong. If WebAssembly works on EOS, then I think that it'll be the same for Ethereum. Just my opinion