I respectfully correct you here. The eosio software has zero to do with token distribution, here I correct you to refer to EOS network/token which I agree has a horrible genesis distribution and therefore very top heavy (whale) control/reward. The distribution of the EOS ICO token has no tie to the underlying eosio blockchain software which is being used in many private networks without any token at all.

Secondly… I agree it is quite misleading to say “store in the user’s RAM” which sounds like it’s on my laptop’s RAM, it is data stored in blockchain state (not in blocks) and is in every node operator’s physical server RAM. However on eosio software, the contract developer has the option to charge any number of accounts (either the contract account itself or any of the N number of accounts which have signed to authorize the executing transaction, there is no single msg.sender on eosio)… it’s a much more sophisticated/powerful/complicated/convoluted/etc.. resource management system than Ethereum.

There are pros/cons to both resource models and I won’t try to preach here because I am a fan of both, but I don’t think it’s fair to make blanket and inaccurate statements like “it’s the same resources” when I can say that I understand both quite well and that despite being similar they are not the same resources.

(Source: I am lead developer of the Telos EVM, which is an EVM implemented as an eosio smart contract. It’s got full EVM RPC feature parity with .5 second block times and no front running. I’ve had to reconcile the resource model of EVM/gas within the eosio software runtime over the past several months 🤯)