11–20 of 42 posts
Uh oh, you said "Blockchain". You have now triggered the Hacker News commentariat.
Looks like you were right. Personally, I would have gone with "WASI-Flavored Blockchain" in any case.
The linked article is quite interesting, but because it's blockchain related the HN groupthink will dismiss it outright.
Earlier quoted context omitted.
Did you read the article? It's got a lot of good information on how code runs on the ethereum virtual machine. And the benefits of using something like WASI. Even if you hate block chain, it's still fascinating.
Why would you use ethereum when you can use Amazon web services instead? Is it because when we use ethereum, the price of eth goes up?
Though the article author omits it, EOS mainnet runs on LLVM and WASM contracts and executes about 1000tx/s today.
A more powerful financial VM is needed e.g. for on-chain order books.
More about use cases vs. databases can be found in my article
https://tokenmarket.net/news/opinion/capital-markets-upcomin...
Earlier quoted context omitted.
Looks like you were right. Personally, I would have gone with "WASI-Flavored Blockchain" in any case.
Doesn't matter, somehow the word blockchain causes normally rational technologists to immediately close their minds and start convulsing in their chairs in an epileptic fit. The linked article is quite interesting, but because it's blockchain related the HN groupthink will dismiss it outright.
For fuck's sake.
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…
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.
"Slow Database"-Flavored WASI Any time you see the word "blockchain" replace it with "Slow Database" in your head and see if it still makes sense.
For fuck's sake.
> the runtime translates WASI args_get and args_sizes_get
> for the zeroth arg to the blockchain address() function.
There is nothing intuitive about that for me.
In most languages, exposing the blockchain interface as a module feels like it would be a significantly cleaner implementation. If I want to compile against different targets I'd prefer to wrap that module as a library behind my own interface. I can then swap out the implementation at compile time.
"Slow Database"-Flavored WASI Any time you see the word "blockchain" replace it with "Slow Database" in your head and see if it still makes sense.
"Slow Database"-Flavored WASI Any time you see the word "blockchain" replace it with "Slow Database" in your head and see if it still makes sense.
The message on the Alibaba site said:
"Attention: Tracking information is supported by the Alibaba Global Trade Blockchain. It may be delayed for 1-2 days."