Here comes when you are asking about the real purpose of viper
Vyper is intentionally not Turing-complete for security and overflow checking reasons which are one of the biggest flaws in Solidity.
https://medium.com/coinmonks/is-vyper-a-good-alternative-to-solidity-ac89c33a1d43about webassembly and I don't think if webassembly will be replaced the solidity programming language as ethereum never think to fully migrated from solidity to the another programming language.
Web assembly has an additional advantages that can be combined with Vyper or Solidity.
Webassemblys is commonly used in execution the smartcontract.
If Vyper is more secure than Solidity, then I wonder why isn't it very popular? I've seen a lot of support and documentation for a programming language (Solidity) that's flawed by design, while not many developers are aware of Vyper. Anyways, I think WebAssembly might be a better option since it's a well-known programming language within the mainstream world. It's been tried-and-tested over the years, unlike Vyper and Solidity which came into inception a few years ago. With so many security flaws on smart contracts today, it's necessary to adopt a language that puts security first above all else. Vyper should be marketed/promoted more often, to make the Ethereum blockchain more secure. Formal verification is what's needed for decentralized applications to become truly censorship-resistant.
In the end, ETH developers will determine which languages will be suitable for deployment of dApps and which are not. If it were me, I'd implement popular programming languages that have a large number of developers working on them. Adopting JavaScript, Python, and even C++ for smart contract development seems like the best way to achieve security like never before. In this regard, NEO is ahead of Ethereum. But time will tell us, if Ethereum will be able to maintain its place in the mainstream world according to its development, innovation, and adoption.
host independence, security sandbox and overall simplicity make it an ideal runtime for smart contracts
https://blog.scottlogic.com/2019/11/26/webassembly-on-the-blockchain.htmlEthereum has also made a trial smartcontract engine that is based on the webassembly and according from some news if that will be launched next year.
All of this is interesting information. Thanks, mate. I'll go with WebAssembly for smart contract development as it'll the next big thing in the Blockchain industry. If EOS has adopted the programming language in the first place, it means that it must the best solution for smart contracts right now. It's no wonder why ETH devs have decided to do the same. With due time, the EVM will be phased out while eWASM is introduced into the Blockchain. This may be sooner than we've expected as the ETH team has successfully forked into "Istanbul" a while ago.
Nonetheless, I'll be locking this thread as my problem has been solved. I'd gladly receive any additional inputs via PM.
