ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> squeak-list
squeak-list
Re: Very bad about Squeak in blogosfere
by Todd Blanchard other posts by this author
Aug 11 2007 5:42PM messages near this date
Re: Very bad about Squeak in blogosfere | Re: Very bad about Squeak in blogosfere
That's right.  And all the other platforms are completely bug free.   
Why I've never decompiled an entire java application server to work  
around a fatal bug or anything.  I mean, there would be no need.  And  
it would be illegal besides.

Oh - except I have.

FWIW, the internet's largest retailer survived the x-mas buying  
season a couple years ago with a newish app server written in C++  
that had an uptime during peak load of something less than 15 minutes  
due to memory exhaustion.  So there's one definition of "production  
ready" for you.

-Todd Blanchard

On Aug 11, 2007, at 3:15 PM, 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."
> 
> 
> 
> 
>  -- 
>  Janko Mivšek
>  AIDA/Web
>  Smalltalk Web Application Server
>  http://www.aidaweb.si
> 
Thread:
Janko Mivsek
Jason Johnson
John M McIntosh
Colin Putney
Andreas Raab
goran
Brad Fuller
Juan Vuletich
Keith Hodges
Jason Johnson
Igor Stasenko
goran
Igor Stasenko
Edgar J. De Cleene
Jason Johnson
Edgar J. De Cleene
Hilaire Fernandes
Andreas Raab
Hilaire Fernandes
Stephane Ducasse
goran
tim Rowledge
Blake
Ivan Tomek
Craig Latta
Ron Teitelbaum
Craig Latta
Ivan Tomek
Stephane Ducasse
John Almberg
Todd Blanchard
Klaus D. Witzel
Bakki Kudva

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved