You are viewing a single comment's thread from:

RE: Reponse to Vitalik's Written Remarks

in #eos7 years ago

If we take away personal vendettas (which I'm not interested in, although I know they are part of human nature and they appear, in more or less concealed forms) I think we have an interesting debate here.

Ethereum and the "BitShares ecosystem" are 2 major platforms which proved their validity for specific use cases. Ethereum brought a turing complete machine on top of the blockchain, allowing a higher degree of flexibility and innovative uses of the blockchain, which, until then, was just a highly reliable ledger. Bitshares (and its trail, Steemit and PeerPlays) brought up the rise of DPoS, which proves to be a more adapted model of governance than PoW (which is, in my opinion, the biggest flaw of Ethereum so far).

I think both platforms helped tremendously with the adoption of cryptos, but each from its own angle.

It's hard to talk about EOS while it's not yet out (in my defense, I tried to compile it last evening, but stopped at dependencies, will give it a try this week again) but I think we're very close to a "quantum leap". My definition of a "quantum leap" means a reorganization of the game in such a way that old players will be simply kicked out. By old players I mean Bitcoin (and the plethora of hundreds of colored coins which are using the same codebase, hence the same governance model).

This quantum leap may appear when the power of the smart contracts of Ethereum is matched with the DPoS approach of BitShares. Ethereum has Casper in development. EOS is already on top of Graphene (although I understand that even this part is already upgraded).

Both platforms are somehow head to head.

I made this long introduction only to say that, in my opinion, neither @dan or Vitalik have the answers about which platform is gonna win.

But the end user. That's why I think it's crucial for EOS to deliver. Something. Fast.

Sort:  

try the docker setup, since it's been corrected, setup is a breeze (albeit still a bit time-consuming). if you want to try and build "by hand", try following the Dockerfile template step-by-step. That's what I've done, and both counts I got it working. But if you just want easy-peasy, definitely, just go the docker route.