Much of the stability issues are not related to speed but to the conversion to 64-bits,
What i see on Eliot web pages are these most often occured words:
fast ( cogblog ) double its speed ( VW ) chip design support ( hic current company )
But, where are the nice and beutiful high ideas like these from Allan Kay and others? Where are final simlicity and usability?
Sorry this Eliot thinking and programming style ( assembler like thinking and supit overoptimizations ) is leading to some kind of all asociated programmers hell ... COG, SPUR whatewer next - he is the number 1. in Open VM and it seems nobody else is care about where it leads and how to change it
which is *critical* for our community since over time modern operating
systems are making it harder to run 32-bit applications. A lot of the complexity is probably in the Cog-JIT, so perhaps StackInterpreter build of the VM would provide the balance of stability and speed you desire (@All, how would you rate that option?)
Maybe i will try anything where Eliot is not putting his hands.
btw, again I ask...
- Which OS version were you running Pharo on?
Pharo 6.1 on Debian Linux
- Were you running 32-bit or 64-bit Pharo?
Both version, old images and vm work OK
- Which links did you download Pharo from? i.e. what is the version/date
of both VM and Image? Often we can advise that specific VM/Image has a known bug that has since been fixed.
I will try squeak, and then give you my opinion. But i preffer Pharo for Seaside support and style and more proffesional look of webpage and previous good images and vms.
Jan. www.mageo.club