Rumors on Reddit that Ethereum scraps Serpent. CounterParty fares any better?
Quote
Serpent has lost funding. Some projects have been written in Serpent, but according to Vitalik:
I personally will not have time to continue Serpent development at anything more than the current glacial pace [...]
Unless someone from the Counterparty community wanted to maintain Serpent, it's dead.
It should be possible to fork cpp-ethereum and make Solidity compatible with Counterparty, but the severe limitations in Solidity make me question Ethereum's programmable contract concept.
On the one hand the core concept itself is quite vulnerable to language ecosystem takeovers, because these are miniscule, poorly maintained designer languages based on experimental compilers and VMs. OTOH is the concept of Turing complete code really that much better than a semi-restricted DSL, or even hard coding features into the protocol? If your idea of Turing complete is Python, well Serpent is downright bad. It lacks basic programming features and is in general the opposite of confidence inspiring. Solidity is not much better. They still don't have arrays. I'm not sure it's even worth copying, because it would be trivial for a better approach to crush whatever sliver of a network effect Ethereum has with something better written or written with a better architecture.
[...]
Crafting beautiful UX is infinitely more valuable than offering a Turing Complete™ platform.
Isn't it more viable for anyone with an interesting "contract" idea to just visit https://github.com/CounterpartyXCP/counterpartyd and create a damn pull request? What is so hard or bad about that? It works plenty well for Bitcoin. Who are the industry leaders who don't think that's good enough?
I personally will not have time to continue Serpent development at anything more than the current glacial pace [...]
Unless someone from the Counterparty community wanted to maintain Serpent, it's dead.
It should be possible to fork cpp-ethereum and make Solidity compatible with Counterparty, but the severe limitations in Solidity make me question Ethereum's programmable contract concept.
On the one hand the core concept itself is quite vulnerable to language ecosystem takeovers, because these are miniscule, poorly maintained designer languages based on experimental compilers and VMs. OTOH is the concept of Turing complete code really that much better than a semi-restricted DSL, or even hard coding features into the protocol? If your idea of Turing complete is Python, well Serpent is downright bad. It lacks basic programming features and is in general the opposite of confidence inspiring. Solidity is not much better. They still don't have arrays. I'm not sure it's even worth copying, because it would be trivial for a better approach to crush whatever sliver of a network effect Ethereum has with something better written or written with a better architecture.
[...]
Crafting beautiful UX is infinitely more valuable than offering a Turing Complete™ platform.
Isn't it more viable for anyone with an interesting "contract" idea to just visit https://github.com/CounterpartyXCP/counterpartyd and create a damn pull request? What is so hard or bad about that? It works plenty well for Bitcoin. Who are the industry leaders who don't think that's good enough?
http://www.reddit.com/r/counterparty_xcp/comments/2y0apx/contract_news/
Thank you. 
