I'm shooting in the dark here since its a bit hard to grasp...

a. The implications of support alternative bytecode sets

�� �� * Do the alternative bytecode sets run in parallel to normal Pharo bytecodes?

�� �� * Can the bytecode sets be loaded adhoc/dynamically into an Image?

�� �� �� ��or only compiled into the VM?

b. How to implement/work with alternative bytecodes

For (a.) I guess an exciting opportunity is facilitating an Ethereum virtual machine��

running as a Process inside a Pharo image, managed by tools written in Pharo.����

Other languages are already getting in a party which would be good for Pharo to join.

In such a revolutionary domain I expect people are more willing to experiment

with alternative systems like Pharo, and I bet Pharo could excel in that domain.

* https://github.com/ethereum/go-ethereum/blob/master/core/vm/opcodes.go

* https://medium.com/@jeff.ethereum/optimising-the-ethereum-virtual-machine-58457e61ca15

*��https://github.com/pirapira/awesome-ethereum-virtual-machine#evm-implementations

To help (b.), would it be feasible to blog a mini-demo showing how to install/use alternative bytecodes? maybe for something like this simple RPN calculator substitute for "arith.c"...

* https://github.com/philipaconrad/mini-vm/tree/master/examples/arith

* https://github.com/philipaconrad/mini-vm/blob/master/examples/arith/arith.c

��

(a calculator demo could be an interesting adjunct to Sven's calculator tutorial...)

cheers -ben