Philippe Marschall wrote:
> So which parts do we need to fix to make the Semaphore, Socket and
> image freezing problems go away?

For semaphores I'd recommend the fixes that I've posted over the year. 
For sockets I am not aware of any evidence that indicate a socket issue 
(we had a few issues that at first looked like sockets were related but 
turned out not) but I'd like to hear any evidence that points to sockets 
as the cause of problems. As far as I can tell the socket implementation 
is very robust right now. For image freezes -in particular in 
Squeaksource- you probably need to fix the concurrency issues in 
Squeaksource itself. The last time I checked the code was not robust 
enough by far against concurrent modifications (parallel commits etc).

> As for scaling and production quality do you seriously expect me to do
> this for free in my spare time?

That depends on whether or not you seriously expect for example the VM 
people to fix the VM problems in their spare time for free. If the 
answer is yes, then the answer is yes.

> We fixed performance the problems and now run seriously faster than
> source.impara.de while being much bigger.

That's great to hear. I wish you would have told me a couple of months 
ago how to achieve that when I was asking (repeatedly) the same questions.

Cheers,
   - Andreas