> 1. What classes are compatible to other smalltalks? When i follow > mailing-lists of Dolphin, Squeak, VW, VA Magma - there still is a bunch of > porting problems. Why?????? What classes should i give preference to > minimize porting cost?
http://www.seaside.st/community/conventions (Portability) > 2. Interfaces ... hmmm, well ... there are many programmes thinking in > categories of "interfaces", "libraries", "class dependencies", e.t.c. Of > course, Smalltalk is something completely different, but it makes it > difficult for s.b. e.g. coming from Java or C++, to find into Smalltalk > concepts. Gofer - till now, i have just a wage imagination, what it's good > for ... Don't know what you are talking about? > 3. GUI builder. IMHO, it's very easy to build a GUI with morphic. In Squeak, > e.g. i simply generate my input forms with EToys, which can be replaced of > course by a few lines of code typed in by hand ... But for developers coming > from Java, C++ ... the first ask for a GUI builder and XAML e.t.c. There > should be some documentation, that leads programmers, that are willing to > switch over to Smalltalk, into the right direction. Just a few examples, > e.g. how to build a form, that scrolls through some MySQL data sets, really > would help. What about compatibility? Is Morphic portable to other > Smalltalks? No. > 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 > 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
