Smart Contract Programming: Cadence vs Solidity
CADENCE SOLIDITY PROGRAMMING Resource-oriented Object-oriented MODEL Currently, an interpreted language. Planning to compile Cadence down to Move bytecode for running on the Move VM COMPILED OR Compiled by the Ethereum Virtual Machine (EVM) INTERPRETED? CONCLUSION DEALING WITH Use argument labels Write comments CADENCE ARGUMENTS Allows writing in a declarative style WRAPPING NATIVE FLOW can be imported directly without a wrapper ETH often needs to be wrapped into WETH ТОKENS In terms of safety and the likelihood of making errors, Cadence looks like a more attractive programming language Keyword-based and capability-based layers of access Can be implemented via access control lists, or msg.sender ACCESS CONTROL Access depends on what you own Access depends on who you are SOLIDITY Doesn't have built-in preconditions and postconditions Offers imperative programming Built-in for functions PRECONDITION and transactions & POSTCONDITION Use modifier for precondition and event emit and processing for postcondition Since most developers have already turned their hand to working with Solidity and know how to deal with emerging issues, they will still rather give their preference to Solidity for now Use proxy or data separation patterns Configurable and transparent built-in upgradeability UPGRADABILITY Developers have to put in a lot of effort to update smart contracts Inspired by Swift and Rust SYNTAX Inspired by C++, JavaScript, and Python
Smart Contract Programming: Cadence vs Solidity
Source
https://pixe...s-for-nft/Category
TechnologyGet a Quote