You are viewing a single comment's thread from:
RE: EOS application stack update: 4 questions left unanswered
I think they couldn't get the required performance from wren, so chose web assembly instead.
I think they couldn't get the required performance from wren, so chose web assembly instead.
I understand but isn't Wren supposed to be a new language being developed? since it is still being developed it could be customized and tweaked to meet any requirements - or what do you think?
even for established languages, there are always new versions released to be more efficient
I don't know much about either language to be honest, but suspect that since webassembly has much more support its performance will be faster, and they probably need to squeeze every bit out of their platform quicker than they could by waiting for wren to mature.
A few languages can compile to down to webassembly though.