Hi Janko,

all problems are challenges, this was always the case, and I wonder  
<sarcasm>why people are using Croquet (Ubuntu) and bulding Sophie on top  
of Tweak and whatsmore on top of Seaside and software researchers rely on  
Squeak</sarcasm> instead of on J# and other static typers. Perhaps because  
J# has already passed its limits and so now Squeak is evaluated and  
thereby found too good to be true :) even if parts of it look crappy to  
the uninitiated :)

The message in blogosfere is a good enough plan for where to start doing  
something exiting with Squeak :) I understand the problem(s) description  
as, hey here's something todo for you hackers (professional developers).  
Sort of marketing; big vendors get mentioned when they face d%!ed big bugs  
and the headline makes it in the public sphere :)

/Klaus

On Sun, 12 Aug 2007 00:15:13 +0200, Janko Mivšek wrote:

>  From Anonymous on  
> http://factor-language.blogspot.com/2007/08/smalltalk-is-dying.html:
>
> "Anyone who says Squeak is production ready has never used Squeak in  
> production. Recently quite a prominent member of the Squeak community  
> seriously considered moving to Java because he could not get uptimes  
> bigger than a two days. It turned out Delays and Semaphores (!!!) were  
> broken all time along. There are dozens of issues like this. One example  
> is that the settings of the GC are tuned for memory sizes of about 1 MB.  
> Don't even get me started about the 1 GB and 120 MB memory issues which  
> tend to crash the image. Or the bugs in ClassBuilder,  
> InterpreterSimulator, Decompiler, .... You need to have several Squeak  
> images per CPU because there is a limit to the amount of punishment a  
> single Squeak image can take. Squeak itself is heavily forked (Squeak,  
> Croquet, Sophie, SqueakLand, SmallLand, ... ). All the code in the image  
> in unmaintained. There are teams but most of the time they don't even  
> integrate submitted fixes for bugs. Development of these packages has  
> stopped. The same situation for the VM. The only VM that is maintened is  
> the Mac VM. The Windows VM will only get new builds if the maintainer  
> needs some fixes for himself. The Unix VM is unmainted. The maintainer  
> of the main VM code publically stated he will do shit unless someone  
> pays him. Squeak is fully of ugly shit code that has just been hacked in  
> for abandoned experiments. That http server Seaside uses on Squeak?  
> Unmaintained and has bugs with HTTP 1.1. That really is just a small  
> list of issues Squeak has."
>
>
>
>