February 2020 - Pharo-users

Re: [Pharo-users] Pharo image processing library

by Kasper Ãsterbye

Cool! I like that readme. Best, Kasper On 6 February 2020 at 03.26.05, Pablo Navarro (pablo1n7(a)gmail.com) wrote: Hi everyone I put available my code for Image Form in GitHub ( https://github.com/pablo1n7/ImageForm) This afternoon, I did the operations with kernels :D. It's not 100% complete, I'm still working on it. I hope you find it useful and any suggestion is welcomed Best Regards, Pablo. El 25 de ene. de 2020 11:33 -0300, Oleksandr Zaitsev <olk.zaytsev(a)gmail.com>, escribiÃ³: Hello Pablo, Is the code of your library available on GitHub? Could you share the link please? Oleks -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 6, 2020

Re: [Pharo-users] About "it's not pharo but smalltalk"

by horrido

I've never posted to /r/smalltalk. There's no point in preaching to the choir. I posted to /r/programming and everybody there tried to lynch me. Pharo Smalltalk Users mailing list wrote > FWIW I am one of the mods of /r/smalltalk - happy to have material > > Sent from my iPhone > >> On Feb 5, 2020, at 13:12, horrido < > horrido.hobbies@ > > wrote: >> >> Reddit is a strange bird. I have found more resistance to Smalltalk there >> than from any other source on the planet. Moreover, those people *really* >> don't appreciate me evangelizing anything. Consequently, I've avoided >> Reddit >> like the plague. >> >> I don't know what kind of readership exists at Reddit, but they are >> openly >> hostile. So you'll forgive me if I don't lend much credence to what >> Redditors say. >> >> >> >> Pavel Krivanek-3 wrote >>> st 5. 2. 2020 v 20:48 odesÃlatel horrido < >> >>> horrido.hobbies@ >> >>> > napsal: >>> >>>> I learned a long time ago that you can't please everybody. I've heard >>>> the >>>> critics about my evangelism. I've also heard the praise. >>>> >>>> So what am I supposed to do? Listen to the critics and ignore the fans? >>>> >>>> If you're an evangelist, you have to develop a thick skin and follow >>>> your >>>> heart. Otherwise, get out of the kitchen... >>>> >>> >>> You are a victim of your own strong confirmation bias. I hardly can >>> break >>> it but I just want to point out that in the mentioned discussion, there >>> was >>> no fan of you (and there were more people complaining than the two I >>> mentioned). >>> >>> Pavel Krivanek-3 wrote >>>>> st 5. 2. 2020 v 19:02 odesÃlatel horrido < >>>> >>>>> horrido.hobbies@ >>>> >>>>> > napsal: >>>>> >>>>>>> You want to take the Smalltalk heritage as a definition, thatâs ok. >>>> We >>>>>> donât, and thatâs ok too. Is about what we want to do. >>>>>> >>>>>> Who's "we"? >>>>>> >>>>>> Last time I checked, nobody owns Pharo. Pharo is not a bunch of core >>>>>> developers; it's a community. And I believe there are many Pharoers >>>> who >>>>>> share my view. >>>>>> >>>>>> Since I'm a Smalltalk evangelist and not a Pharo evangelist, I guess >>>>>> I >>>>>> shouldn't ever mention Pharo in my blog. After all, if it's not >>>>>> Smalltalk, >>>>>> why should I promote it??? >>>>>> >>>>> >>>>> Pharo 8.0 release Reddit discussion included some feedback you >>>>> may appreciate: >>>>> >>>>> "Thanks. Does this Pharo release removes feature "Richard Kenneth >>>>> Eng"? >>>>> That was the only feature in detriment to such an excellent >>>>> environment >>>> as >>>>> Pharo." >>>>> >>>>> "I really like the idea of pharo's features and smalltalk is quite >>>>> interesting, but I can't help but be put off by the insanely stupid >>>>> marketing culture around it. Most articles about it exaggerate way too >>>>> much >>>>> and seem like they're written by people who were paid to write about >>>> it. >>>>> Or >>>>> maybe I'm reading Medium-cancer too much." >>>>> >>>>> >>>>> >>>>>> In fact, this is disastrous for my JRMPC competition since it's based >>>>>> entirely on Pharo. I'm promoting Smalltalk but pushing Pharo on all >>>> the >>>>>> participating teams??? What the f*ck am I doing?!! >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>>>> >>>>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>> >>>> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 6, 2020

Re: [Pharo-users] About "it's not pharo but smalltalk"

by Todd Blanchard

FWIW I am one of the mods of /r/smalltalk - happy to have material Sent from my iPhone > On Feb 5, 2020, at 13:12, horrido <horrido.hobbies(a)gmail.com> wrote: > > Reddit is a strange bird. I have found more resistance to Smalltalk there > than from any other source on the planet. Moreover, those people *really* > don't appreciate me evangelizing anything. Consequently, I've avoided Reddit > like the plague. > > I don't know what kind of readership exists at Reddit, but they are openly > hostile. So you'll forgive me if I don't lend much credence to what > Redditors say. > > > > Pavel Krivanek-3 wrote >> st 5. 2. 2020 v 20:48 odesÃlatel horrido < > >> horrido.hobbies@ > >> > napsal: >> >>> I learned a long time ago that you can't please everybody. I've heard the >>> critics about my evangelism. I've also heard the praise. >>> >>> So what am I supposed to do? Listen to the critics and ignore the fans? >>> >>> If you're an evangelist, you have to develop a thick skin and follow your >>> heart. Otherwise, get out of the kitchen... >>> >> >> You are a victim of your own strong confirmation bias. I hardly can break >> it but I just want to point out that in the mentioned discussion, there >> was >> no fan of you (and there were more people complaining than the two I >> mentioned). >> >> Pavel Krivanek-3 wrote >>>> st 5. 2. 2020 v 19:02 odesÃlatel horrido < >>> >>>> horrido.hobbies@ >>> >>>> > napsal: >>>> >>>>>> You want to take the Smalltalk heritage as a definition, thatâs ok. >>> We >>>>> donât, and thatâs ok too. Is about what we want to do. >>>>> >>>>> Who's "we"? >>>>> >>>>> Last time I checked, nobody owns Pharo. Pharo is not a bunch of core >>>>> developers; it's a community. And I believe there are many Pharoers >>> who >>>>> share my view. >>>>> >>>>> Since I'm a Smalltalk evangelist and not a Pharo evangelist, I guess I >>>>> shouldn't ever mention Pharo in my blog. After all, if it's not >>>>> Smalltalk, >>>>> why should I promote it??? >>>>> >>>> >>>> Pharo 8.0 release Reddit discussion included some feedback you >>>> may appreciate: >>>> >>>> "Thanks. Does this Pharo release removes feature "Richard Kenneth Eng"? >>>> That was the only feature in detriment to such an excellent environment >>> as >>>> Pharo." >>>> >>>> "I really like the idea of pharo's features and smalltalk is quite >>>> interesting, but I can't help but be put off by the insanely stupid >>>> marketing culture around it. Most articles about it exaggerate way too >>>> much >>>> and seem like they're written by people who were paid to write about >>> it. >>>> Or >>>> maybe I'm reading Medium-cancer too much." >>>> >>>> >>>> >>>>> In fact, this is disastrous for my JRMPC competition since it's based >>>>> entirely on Pharo. I'm promoting Smalltalk but pushing Pharo on all >>> the >>>>> participating teams??? What the f*ck am I doing?!! >>>>> >>>>> >>>>> >>>>> -- >>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>>> >>>>> >>> >>> >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Feb. 6, 2020

Re: [Pharo-users] Pharo image processing library

by Pablo Navarro

Hi everyone I put available my code for Image Form in GitHub (https://github.com/pablo1n7/ImageForm) This afternoon, I did the operations with kernels :D. It's not 100% complete, I'm still working on it. I hope you find it useful and any suggestion is welcomed Best Regards, Pablo. El 25 de ene. de 2020 11:33 -0300, Oleksandr Zaitsev <olk.zaytsev(a)gmail.com>, escribiÃ³: > Hello Pablo, > > Is the code of your library available on GitHub? > Could you share the link please? > > Oleks > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Feb. 6, 2020

Re: [Pharo-users] About "it's not pharo but smalltalk"

by Benoit St-Jean

Here we go again... <rant> What is wrong with you people? Seriously? With this "Pharo is NOT Smalltalk" BS? If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck! To convince yourself, I urge you all to try to evaluate this in any other Smalltalk (Dolphin, Cuis, VisualWorks, LittleSmalltalk, ObjectStudio, VisualAge Smalltalk, IBM Smalltalk, Instantiations Smalltalk, Smalltalk/X, ObjectWorks, Visual Smalltalk Enterprise, Smalltalk Express, Amber Smalltalk, Redline Smalltalk, Smalltalk MT, GNU Smalltalk, you-f*cking-name-it-Smalltalk) to see if it compiles: Transcript inspect. Workspace inspect. Processor inspect. Smalltalk inspect. true inspect. false inspect. thisContext inspect. nil inspect. self inspect. super inspect. Undeclared inspect. #someSymbol inspect. #(1 2 3) inspect. Object allInstances. OrderedCollection class inspect. Behavior inspect. Class inspect. MethodDictionary inspect. Smalltalk garbageCollect. 3@4 inspect. ([ :a :b | a + b ] value: 3 value: 4) inspect. [50 factorial] forkAt: Processor userBackgroundPriority. Now, if you still think that Pharo is NOT Smalltalk, I strongly suggest we remove all the code that was inherited from Squeak (Smalltalk) or inspired/borrowed by/from VisualWorks & others.Â Same thing for the VM : we should build our own from scratch as Squeak and Cuis also use the same!Â And we should assign different numbers to every primitive we do share with all other Smalltalks out there since 1980 : we wouldn't want to be associated with any Smalltalk, right? We don't want any Smalltalk in Pharo, don't we, since it is NOT Smalltalk? Besides, just so you can glady remove all traces of the "forbidden" word or heritage, you must know that the current Pharo 8 images has 1724 references to the global Smalltalk.Â If you dig a little bit deeper (adding comments, deprecated code, the string 'Smalltalk' as well as the #Smalltalk symbol, you'll end up with 5000+ occurrences of the "forbidden word" "Smalltalk" in the current Pharo 8 image.Â Wanna add occurrences of "Smalltalk" in method names as well while we're at it? ;) But hey, Pharo is NOT Smalltalk, right? ;)Â loll Should I create a PR for every occurrence of the forbidden word so we can get rid of that shameful heritage and clean up the image?Â We should also remove the strings Squeak (56 times), Cuis, VisualWorks, VW, VisualAge & others since Pharo is NOT Smalltalk?Â Did I say it enough?Â Pharo is NOT Smalltalk!Â Even if I can load Smalltalk code from SmalltalkHub, SqueakSource and ss3.gemtalksystems.com, Pharo is NOT Smalltalk, do you get it? I can load mcz packages made for Cuis & Squeak but, nonetheless, Pharo is NOT Smalltalk!Â How many times do I have to say it? Imagine the following discussion: A- I heard you bought a new car? B- No I bought a Toyota Corolla. A- So you bought a new car! B- A TOYOTA COROLLA IS **NOT** A CAR. Ain't that discussion & deny stupid enough? I get the impression we constantly have this kind of denial/discussion here...Â A serious case of SSS : Shame of Smalltalk Syndrome. Pharo wants to be different : okay.Â Fine. Cool! But please, stop saying that Pharo is NOT Smalltalk. It is. </rant> // -- ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth GitHub: bstjean Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein)

Feb. 6, 2020

Re: [Pharo-users] About "it's not pharo but smalltalk"

by horrido

I'm not sure ANSI compliance is particularly useful. Nobody develops an application strictly to the ANSI standard. Ben Coman had to port VisualWorks code to Pharo for my JRMPC competition and it wasn't exactly a cake walk. My friend Bob Nemic got confused between VisualWorks and Pharo because of the IDE! There is no standard convention applied to Smalltalk IDEs and, to me, that's a big issue as well. The fact is, the world of Smalltalk is just like the world of Linux. There are enough differences among the various family members that you just have to adapt. It will never be easy. TedVanGaalen wrote > Yes, Esteban, > > maybe I was a bit harsh, in a sense you're right too, > However it becomes blurred then wat Smalltalk really is. > (e.g. I recommend Pharo as Smalltalk to others) > > I would prefer -but who am I- > that all Smalltalk dialects should implement > the ANSI standard as a minimum and at least on > that level stay compatible. > New developments should be built on top of that. > and get incorporated in the ANSI standard at certain points in time. > So that everybody on this planet can work with one Smalltalk. > That makes sense, don't you agree? > > They came very close to that with PLs like COBOL, ANSI C etc. > > Standardization is industrial. No need > to further explain this I guess. > > The f. devil lives in the details, as they say, > and it is exactly those little differences > that makes it very hard to port packages > from one Smalltalk dialect to another. > > In the current situation, that is where everybody wants to > go their own unique way, this has the consequence that > if one Smalltalk dialect disappears (e.g. Squeak, Pharo, > Visualworks, whatever) this would render packages > with often tons of work(e.g. Roassal ?) > worthless because they don't load/work in other Smalltalk > implementations/dialects without rewriting and retesting > the package again. This should not be the case. > > Again, I am impressed by Pharo and really like it. > but for me it goes too far to say that Pharo isn't Smalltalk. > > As a user, I edit classes methods etc in exactly the same > way (syntax) as in most other Smalltalk dialects. > If you would take out the Smalltalk from Pharo all is left > are a few bolts and nuts rendered useless: nothing > to mount it on. > > (Still the differences are currently not that big: > if I can file in st files from Squeak from 2010 and the > only thing I had to change was a datetime property) > (yet another reason I don't use traits is to remain compatible > as much as possible between different Smalltalk implementations) > > my 4 cents. :o) > Regards, thank you. > TedvG > btw > Hard to convince people about this: > Also. nothing should be deprecated. > Old sources should remain compatible. > (Not like in Swift, where I had to rewrite parts of my > apps nearly every year because of deprecation fever) > > > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 5, 2020

Re: [Pharo-users] About "it's not pharo but smalltalk"

by TedVanGaalen

Yes, Esteban, maybe I was a bit harsh, in a sense you're right too, However it becomes blurred then wat Smalltalk really is. (e.g. I recommend Pharo as Smalltalk to others) I would prefer -but who am I- that all Smalltalk dialects should implement the ANSI standard as a minimum and at least on that level stay compatible. New developments should be built on top of that. and get incorporated in the ANSI standard at certain points in time. So that everybody on this planet can work with one Smalltalk. That makes sense, don't you agree? They came very close to that with PLs like COBOL, ANSI C etc. Standardization is industrial. No need to further explain this I guess. The f. devil lives in the details, as they say, and it is exactly those little differences that makes it very hard to port packages from one Smalltalk dialect to another. In the current situation, that is where everybody wants to go their own unique way, this has the consequence that if one Smalltalk dialect disappears (e.g. Squeak, Pharo, Visualworks, whatever) this would render packages with often tons of work(e.g. Roassal ?) worthless because they don't load/work in other Smalltalk implementations/dialects without rewriting and retesting the package again. This should not be the case. Again, I am impressed by Pharo and really like it. but for me it goes too far to say that Pharo isn't Smalltalk. As a user, I edit classes methods etc in exactly the same way (syntax) as in most other Smalltalk dialects. If you would take out the Smalltalk from Pharo all is left are a few bolts and nuts rendered useless: nothing to mount it on. (Still the differences are currently not that big: if I can file in st files from Squeak from 2010 and the only thing I had to change was a datetime property) (yet another reason I don't use traits is to remain compatible as much as possible between different Smalltalk implementations) my 4 cents. :o) Regards, thank you. TedvG btw Hard to convince people about this: Also. nothing should be deprecated. Old sources should remain compatible. (Not like in Swift, where I had to rewrite parts of my apps nearly every year because of deprecation fever) -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 5, 2020

Re: [Pharo-users] About "it's not pharo but smalltalk"

by horrido

I beg to differ. I believe it is possible to re-energize Smalltalk. I believe /marketing/ is the key. Read https://medium.com/@richardeng/yes-it-is-allow-me-to-explain-dbd33ef0ff21 I've always known this was an uphill battle. Ultimately, you may be right, but I choose to be more optimistic. My philosophy is that it's better to have tried and failed, then to not have tried at all. Pavel Krivanek-3 wrote > st 5. 2. 2020 v 20:42 odesÃlatel horrido < > horrido.hobbies@ > > napsal: > >> > It is your initiative, you should know, nobody asked you to do it >> >> Well, that's a peculiar attitude. There are many, many programming >> language >> evangelists and I don't think anybody "asked" them to do it. They do it >> for >> the love of the language. >> >> I hear what you're saying, and I understand fully. I just don't agree >> with >> it entirely. >> >> I think it's short-sighted. Smalltalk has long been criticized for being >> a >> secluded island, and now you want to do the same for Pharo? Even as I try >> to >> build bridges to the island? >> >> You could ban everybody from this forum who aren't focussed 100% on Pharo >> and you'd have a much smaller community. You could ban everybody who is a >> Smalltalker. The result is a much more tightly focussed forum, clean and >> free from distractions. Fine. But what is the long-term cost? >> >> Smalltalk evangelism would come to an end. Why? Because frankly nobody is >> interested in the other Smalltalks. Pharo is where all the action is. >> >> And without Smalltalk evangelism, I don't see a path for Pharo becoming >> more >> than a niche language. Pharo doesn't show up an *any* language popularity >> index. At least Clojure, Erlang/Elixir, and Haskell are in the top 30 in >> several places. >> >> At Indeed, there are 18 job postings in the United States that mention >> Smalltalk, and none for Pharo. Even Clojure has 404, Erlang has 274, and >> Haskell has 519, pathetic though these numbers are. >> >> Yes, I also understand that there are many Pharoers who don't care about >> remaining niche. That's a tragedy. >> >> I would rather not have wasted the last five years of my life. >> > > Sorry to say that but you wasted the last five years of your life. Google > trends for Smalltalk: > > [image: chrome_JbORSPVuGv.png] > > Smalltalk is dead. Dead and no-one can change it. It is an interesting > historical curiosity. You are trying to sell a dead horse. > And yes, Pharo is an irrelevant niche language and it is very unlikely > that > it will change in future. It definitely will not change If it will be > promoted the way you do that. > > -- Pavel > > >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> > > > chrome_JbORSPVuGv.png (11K) > <http://forum.world.st/attachment/5111235/0/chrome_JbORSPVuGv.png> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 5, 2020

Re: [Pharo-users] About "it's not pharo but smalltalk"

by Pavel Krivanek

st 5. 2. 2020 v 20:42 odesÃlatel horrido <horrido.hobbies(a)gmail.com> napsal: > > It is your initiative, you should know, nobody asked you to do it > > Well, that's a peculiar attitude. There are many, many programming language > evangelists and I don't think anybody "asked" them to do it. They do it for > the love of the language. > > I hear what you're saying, and I understand fully. I just don't agree with > it entirely. > > I think it's short-sighted. Smalltalk has long been criticized for being a > secluded island, and now you want to do the same for Pharo? Even as I try > to > build bridges to the island? > > You could ban everybody from this forum who aren't focussed 100% on Pharo > and you'd have a much smaller community. You could ban everybody who is a > Smalltalker. The result is a much more tightly focussed forum, clean and > free from distractions. Fine. But what is the long-term cost? > > Smalltalk evangelism would come to an end. Why? Because frankly nobody is > interested in the other Smalltalks. Pharo is where all the action is. > > And without Smalltalk evangelism, I don't see a path for Pharo becoming > more > than a niche language. Pharo doesn't show up an *any* language popularity > index. At least Clojure, Erlang/Elixir, and Haskell are in the top 30 in > several places. > > At Indeed, there are 18 job postings in the United States that mention > Smalltalk, and none for Pharo. Even Clojure has 404, Erlang has 274, and > Haskell has 519, pathetic though these numbers are. > > Yes, I also understand that there are many Pharoers who don't care about > remaining niche. That's a tragedy. > > I would rather not have wasted the last five years of my life. > Sorry to say that but you wasted the last five years of your life. Google trends for Smalltalk: [image: chrome_JbORSPVuGv.png] Smalltalk is dead. Dead and no-one can change it. It is an interesting historical curiosity. You are trying to sell a dead horse. And yes, Pharo is an irrelevant niche language and it is very unlikely that it will change in future. It definitely will not change If it will be promoted the way you do that. -- Pavel > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Feb. 5, 2020

Re: [Pharo-users] About "it's not pharo but smalltalk"

by horrido

Reddit is a strange bird. I have found more resistance to Smalltalk there than from any other source on the planet. Moreover, those people *really* don't appreciate me evangelizing anything. Consequently, I've avoided Reddit like the plague. I don't know what kind of readership exists at Reddit, but they are openly hostile. So you'll forgive me if I don't lend much credence to what Redditors say. Pavel Krivanek-3 wrote > st 5. 2. 2020 v 20:48 odesÃlatel horrido < > horrido.hobbies@ > > napsal: > >> I learned a long time ago that you can't please everybody. I've heard the >> critics about my evangelism. I've also heard the praise. >> >> So what am I supposed to do? Listen to the critics and ignore the fans? >> >> If you're an evangelist, you have to develop a thick skin and follow your >> heart. Otherwise, get out of the kitchen... >> > > You are a victim of your own strong confirmation bias. I hardly can break > it but I just want to point out that in the mentioned discussion, there > was > no fan of you (and there were more people complaining than the two I > mentioned). > > Pavel Krivanek-3 wrote >> > st 5. 2. 2020 v 19:02 odesÃlatel horrido < >> >> > horrido.hobbies@ >> >> > > napsal: >> > >> >> > You want to take the Smalltalk heritage as a definition, thatâs ok. >> We >> >> donât, and thatâs ok too. Is about what we want to do. >> >> >> >> Who's "we"? >> >> >> >> Last time I checked, nobody owns Pharo. Pharo is not a bunch of core >> >> developers; it's a community. And I believe there are many Pharoers >> who >> >> share my view. >> >> >> >> Since I'm a Smalltalk evangelist and not a Pharo evangelist, I guess I >> >> shouldn't ever mention Pharo in my blog. After all, if it's not >> >> Smalltalk, >> >> why should I promote it??? >> >> >> > >> > Pharo 8.0 release Reddit discussion included some feedback you >> > may appreciate: >> > >> > "Thanks. Does this Pharo release removes feature "Richard Kenneth Eng"? >> > That was the only feature in detriment to such an excellent environment >> as >> > Pharo." >> > >> > "I really like the idea of pharo's features and smalltalk is quite >> > interesting, but I can't help but be put off by the insanely stupid >> > marketing culture around it. Most articles about it exaggerate way too >> > much >> > and seem like they're written by people who were paid to write about >> it. >> > Or >> > maybe I'm reading Medium-cancer too much." >> > >> > >> > >> >> In fact, this is disastrous for my JRMPC competition since it's based >> >> entirely on Pharo. I'm promoting Smalltalk but pushing Pharo on all >> the >> >> participating teams??? What the f*ck am I doing?!! >> >> >> >> >> >> >> >> -- >> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 5, 2020