Feb. 19, 2013
2:08 p.m.
There is a potential problem for me with 2.0: It includes NativeBoost/Athens.... As I am targeting iOS running on a StackVM, am I stuck to 1.4? Is there anything to do to ensure that Pharo 2.0 is not a dead end for such developments? Maybe this is just me scaring myself... There is value in an all software Pharo stack. Which is why I went that way in the first place. Phil