Blockchain-Flavored WASI

Post by jacobush » Sun, May 26, 2019, 8:19 AM UTC

miohtama wrote: post #14

jacobush wrote: post #4

Earlier quoted context omitted.

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…

An 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.

That is also totally insane.

Post by jacobush » Thu, May 30, 2019, 8:36 AM UTC

miohtama wrote: post #14

jacobush wrote: post #4

Earlier quoted context omitted.

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…

An 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.

But it’s not very optimized. It’s very low level and you have to add defensive code, taking up space.

Re: Blockchain-Flavored WASI

Re: Blockchain-Flavored WASI