> 4. Multitasking, green threads, ... There are really missing some pointers,
> howto code e.g. a background process that is fetching some data from e.g.
> MySQL or reading/writing large files, sending data over network - �without
> freezing the GUI.
[ self writeLargeFile ] fork
This is not actually true if the database driver has to use FFI to communicate to an external librarym since FFI locks the complete VM while a function is being executed. So, in certain percentage, he is right.
�
> 5. Standards: XML-RPC, SOAP, RMI, CORBA, .... encryption (SSL) ... Without
> having a precise idea, where to find working examples to exchance data with
> other systems, i would hesitate to begin to do projects with Pharo/Squeak
> ...
>
> 6. Databases: Magma seems to be fine as database, but also dog slow. I
> really hesitate to start serious projects with Magma.
GemStone/S
> 7. Speed, Memory consumption, Quality of modern algorithms: When working
> with Seaside, PIER ... that stuff is dog slow
Compared to what?
> That makes webhosting e.g. on vservers absolutely impossible,
> the whole system quickly becomes unstable. IMHO in Pharo there are routines,
> that really waste a lot of memory, that could be programmed in a more
> intelligent way, expecially collection's algorithms ... ;-)
There is a submission process for improvements. Feel free to contribute.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch