Guido, I doubt anyone here would say that Pharo is perfect, but "very unreliable???" That is simply not true. There is polling, and there should not be - I am probably as outspoken as any on that point.
Overall, Pharo works very well and is being improved on multiple fronts. Bill ________________________________________ From: [email protected] [[email protected]] on behalf of Guido Stepken [[email protected]] Sent: Sunday, November 06, 2011 6:00 PM To: [email protected] Subject: Re: [Pharo-project] Pharo suffers internal Traffic Jams ... > Reading was not a problem. But I have problems to understand what I am > supposed to understand? > > Norbert You are just coder, no software architect, right? Ever tried Pharo 1.3 on a older machine, e.g. P75 with 32 MBytes RAM, some load on Seaside? Funny effects occurring... machine hangs, crashes, spends lots of time in useless functions, unneccessarily locking resouces, memory pumping, eating up resources while waiting for e.g. database answer, spending increasing amount of time (up to 98%) in removing garbage .... It's a good way of identifying unmatured software designs. Colliding mental models (e.g. event driven vs. polling) Such things happen, when all members are just coding, fixing, refactoring, without bothering about algorithms, that still work reliable at low memory and high load. Pharo at the moment is still very unreliable. Sorry to say that! Think about, why FreeBSD works reliably even at a load of 50, whereas other OS stop working. regards, Guido Stepken
