4 ms·
Agreed, though what's really fucked up is the native Ethereum language and machine. Almost anything is an improvement on that. I still don't know what to use an
by jacobush 7y ago
Agreed, though what's really fucked up is the native Ethereum language and machine. Almost anything is an improvement on that. I still don't know what to use any of that for though. :-/
Edit: yes I mean Solidity. I mean, it's cool that it works, but look at it, it's insane. They could have picked just about any language, including assembler, Lisp, Lua, Javascript, Visual Basic, LLVM bytecode, whatever and would have been better off. But over time there will evolve compilers which can from another input language provably (-ish in most cases) produce safe output.
- xrd 7y agoCare to say more? Solidity? If so, I agree. That's why this article is interesting. You are right, the article doesn't address why ethereum might not solve any real problems, if you feel that way.
- miohtama 7y agoAn EVM smart contract bytecode is usually 2kB - 4kB. You can think it as DSL optimised for its use case. EOS contracts are 250kB because they suck in C++ stdlib, templates or what not. There are benefits of having compact bytecode performance wise: cache pressure, price of on-chain storage and so on.