> Please note that Pharo is not even yet in beta, so some of the snags > you mention will no doubt get fixed as the feature list finalizes. > As an open source project, there will be a certain amount of bias > toward what is important to the heavy contributors. I hope those > will include organizations such as yours to push Pharo in the > direction of a stable performance-oriented environment on top of > which a mix of commercial and academic projects will flourish.
Yes, yes, yes :-) This is why I showed up here, at the moment it is just me probing around in my private time but the motivation is to lobby for considering its use at my work. I assume there will be loads of additions required before we can even use it in the small there and clearly such additions won't just appear unless we contribute heavily towards them ourselves. (Off the cuff I'm thinking of requirements like full SOAP(all versions!) with support tools, multiple windows, COM interfacing etc, etc, but I need to cut my teeth on the basics first before I want to start discussing such things here). Baby steps will do just fine ;-) Thanks! Reinout ------- _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
