Ben Coman wrote > it seems some people want to push PharoLauncher to *be* Pharo. > To me this seems a poor strategy… This seems strange to me and highly > likely to confuse newcomers.
Yes, this was already discussed at length on the ML. The term Pharo already has a meaning: a vm + image containing both an OOP language (is it Smalltalk or Smalltalk inspired? Please don't actually answer that lol) and IDE written therein - or you could call it prototype Dynabook software. If we now try to redefine the above (or really overload, because the former definition will still coexist) to mean an app that manages images, it may just be the final straw to make sure that no one ever will be able to give any acceptable answer in less than 2038 hours to the question: What is Pharo? ;) But just in case we step into the quicksand even further, in this dystopian future you can just copy paste this definition: Pharo is a Pharo app that manages Pharo images, which can be used to make Pharo apps, which can be used to manage Pharo images, [which can be used to make Pharo apps, which can be used to manage Pharo images]* ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
