> > > It looks like this topic comes and goes since 20 years: new features added, > image growth then/or it becomes hard to unload ; on Squeak then now with > Pharo at a much higher rate. > > We all know about the right approach (GNU Smalltalk, CUIS Smalltalk),
I will not comment on that and suggest you to code with such systems. but it > is not the road chosen with Pharo and it is becoming extremely uninteresting > for me to code on DrGeo now. Fair. Do not do it. > So far I fell ashame to ship end user > application with a 50MB DrGeo image, knowing only 10% has purpose related to > DrGeo domain. When situation improves, motivation may come back. For this > same reason and other, I turned to Python for a planed programming course to > mid high school students. Good luck. I was teaching python to my son and I have to explain to him that a set cannot contain a set or any object, that length is not a message and plenty of other nice things. > > How the image is considered in the Pharo team? A kind of sacred place, > where stuff are added following a few guidelines (you will not duplicate > features but replace/imprive/whatever -- aka funny shortcut mess, you will > make your code unloadable, etc...) or just like a forum where teams add > feature according to projects or vision. Hilaire if you believe that we are a bunch a morons this is up to you. Now we do pay a lot of attention to our system but our ressources are scarce and we try to satisfy many different concerns. And we do not get that much help from people. You see doing something real and of good quality takes a lot of time and energy. And I think that we are successful. It does not mean that we cannot improve. > Sorry to discuss these topics again, really don't want but still need to > share a few thoughts. I would prefer that you share some code and Pull Requests that always the same complains. But you can. Stef
