How to Learn Solidity: The Ultimate Ethereum Coding Guide
1–10 of 56 posts
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#2Now this truly is a job for the future..
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#3And remember, that there's a special function called VIP() .
This is an implied function that wraps around your full code. This is instantiated if/when core founders are losing money on a function that possibly had a bug in it. This function returns the wrapped function, under the guise of a new blockchain, with invalidations applied to all 'unintentional' side effects of bad or buggy code.
It happened with the DAO, because founders lost too much money. Just be aware, that VIP() can happen to your code, regardless if your implementation is a bug or intentional. Wrong people losing money means VIP() returns successful.
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#4[deleted]
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#5One of the main Ethereum co-founders is working on a new experimental contract language targeting the Ethereum Virtual Machine called Viper which still seems to be under relatively active development[1].
Why pick Solidity if Viper and other languages like Low-level Lisp-like Language (LLL) by Consensys[2] are around the corner? Or is this just a matter of language flavour similar to how anybody can pick from a plethora of languages targeting the JVM (Clojure, Scala, Java, etc.)?
[1] https://github.com/ethereum/viper
[2] https://media.consensys.net/an-introduction-to-lll-for-ether...
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#6And remember, that there's a special function called VIP() . This is an implied function that wraps around your full code. This is instantiated if/when core founders are losing money on a function that possibly had a bug in it. This function returns the wrapped function, under the guise of a new blockchain, with invalidations applied to all 'unintentional' side effects of bad or buggy code. It happened with the DAO,…
To me, this turns me off to the entire tech, no matter how stupid and kneejerk that sounds. If the biggest draw to get me using your technology (immutable contracts) is actually not true, then I'm less inclined to give it a shot outside of novelty value.
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#7And remember, that there's a special function called VIP() . This is an implied function that wraps around your full code. This is instantiated if/when core founders are losing money on a function that possibly had a bug in it. This function returns the wrapped function, under the guise of a new blockchain, with invalidations applied to all 'unintentional' side effects of bad or buggy code. It happened with the DAO,…
Your Solidity contracts can run on Ethereum Classic, which you can be confident won't be forked since its users tend to believe in the principle of the immutability of the code.
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#8And remember, that there's a special function called VIP() . This is an implied function that wraps around your full code. This is instantiated if/when core founders are losing money on a function that possibly had a bug in it. This function returns the wrapped function, under the guise of a new blockchain, with invalidations applied to all 'unintentional' side effects of bad or buggy code. It happened with the DAO,…
To me, this turns me off to the entire tech, no matter how stupid and kneejerk that sounds. If the biggest draw to get me using your technology (immutable contracts) is actually not true, then I'm less inclined to give it a shot outside of novelty value.
Maybe the immutability is not 100% now, but it will be when the technology is finalized, which will take a few more years. The fork to save DAO funds was a good thing, because otherwise too much ETH would have been in the hands of an attacker. The ETH distribution would have been skewed. That's all.
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#9One of the main Ethereum co-founders is working on a new experimental contract language targeting the Ethereum Virtual Machine called Viper which still seems to be under relatively active development[1]. Why pick Solidity if Viper and other languages like Low-level Lisp-like Language (LLL) by Consensys[2] are around the corner? Or is this just a matter of language flavour similar to how anybody can pick from a pletho…
Viper is not completed, and it might never be completed.
Solidity is here now, and the demand for Solidity developers is growing by the hour.
Re: How to Learn Solidity: The Ultimate Ethereum Coding Guide
#10And remember, that there's a special function called VIP() . This is an implied function that wraps around your full code. This is instantiated if/when core founders are losing money on a function that possibly had a bug in it. This function returns the wrapped function, under the guise of a new blockchain, with invalidations applied to all 'unintentional' side effects of bad or buggy code. It happened with the DAO,…
Your Solidity contracts can run on Ethereum Classic, which you can be confident won't be forked since its users tend to believe in the principle of the immutability of the code.
The classic branch is still susceptible to the same problem, though. They didn't fork because of the DAO, but who's to say they won't fork because they don't like the result of a different contract?
If I'm going to trust the enforceability of my contract to some group of people, I trust the established legal system--warts and all--much more than the mob rule of the Ethereum crowd.