May 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Saving a Smalltalk Project

by Sean P. DeNigris

horrido wrote > I am in half minds > to migrate to a platform which uses a more mainstream language (Java / > Python) as I have been getting some strange reactions from Angel Investors > / > VCs and mainstream developers. OT: It's ironic that Smalltalkers are often accused of NIH syndrome, but the first reaction of people from less "productive" languages/systems is to rewrite a working Smalltalk app in their language of comfortâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 5, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Sean P. DeNigris

Richard Sargent wrote > No. Please, really no. As much as I appreciate (and share) the passion for Smalltalk, you did not AFAICT address my reasoning for not applying the no-acronym *guideline* in this case, namely: >> Since the argument IIUC is that "a >> general user won't know the domain well enough to understand the >> acronym", >> would they understand "abstractSyntaxTree"?! That, to me, is as opaque as >> the acronym for one not acquainted with the domain, and may buy us little >> at the cost of a good amount of extra typing. Richard Sargent wrote > a disambiguation page with a lengthy list IMHO this is irrelevant. My proposal included a method comment, which would provide the google-able term, as well as potentially a good enough summary that one wouldn't have to leave the image. The fact that the method belongs to CompiledMethod is the disambiguation. The internet is meaningless and flat compared to the context and structure of a ST image. Richard Sargent wrote > Do not use comments embedded *inside* methods to cover for naming the > method badlyâ¦ Also, if one Googles an acronym How is a harder-to-type thing that the user doesn't understand but is easier to google better than a comment that gives the necessary context right in the image? My ideal image would avoid the need to Google as much as possible, suggesting a comment either way, so nothing lost. There's nothing inherently "bad" about an acronym. For example, no one's been banging down the door to rename "JPEGReadWriter" to "JointPhotographicExpertsGroupReadWriter". In that case, it's because the acronym is so well-known, but what I'm asking whether #ast is a similar candidate for exception because it is so unknown (i.e. compiler domain-specific) that a user is likely to know either the term and the acronym or neither. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 5, 2018

Re: [Pharo-users] [Seaside] [ANN] ChartJs for Seaside v1.0.0

by Cyril Ferlicot D.

Le 04/05/2018 Ã 22:06, Smalltalk a Ã©critÂ : > Cyril, > > Thanks for sharing this. Very cool ! > > I'm using a very basic package to render charts with SVG (scalable > vector graphics) build by my self. > > Now i think i will switch to ChartJs. I'll try to load it to Seaside for > GemStone. Great! :) I never really used gemstone so there will be some troubles probably. If you open issues describing them I can correct them when I'll have the time. > > regards, > bruno > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Libre de virus. www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Cyril Ferlicot https://ferlicot.fr

May 5, 2018

Re: [Pharo-users] [Job] Pharo developers wanted in Toronto

by Norbert Hartl

> Am 05.05.2018 um 03:02 schrieb Ben Coman <btc(a)openinworld.com>: > > On 4 May 2018 at 22:00, <aglynn42(a)gmail.com <mailto:aglynn42@gmail.com>> wrote: > Telna is looking for developers with Smalltalk experience, preferably Pharo, in Toronto Canada. > > The role is listed on indeed.ca <http://indeed.ca/> if anyone is interested. > > Andrew Glynn > > Thanks Andrew. > > Because people are generally interested in seeing where Pharo is being used, > I think there is value in copying here the whole job post for the mail archives. > If we get to the point where there are too many such posts.... actually that would be a great outcome and we can review policy then. > > Personally I find this usage very interesting... > And it is not really new. Just have a look at https://pharo.org/success/Sysmocom <https://pharo.org/success/Sysmocom> Norbert > cheers -ben > > ----- > Telna is a global network operator that focuses on providing "out of the box" connectivity to devices, machines, users and manufacturers. We are changing the way networks operator, by focusing on scalable software-defined networks that can be deployed anywhere in the world in minutes rather than years. > We are looking for Software Engineers to join our network team to design and develop the core tools that drive our "Network as a Service" platform. Development experience in smalltalk is mandatory. > > This is a unique opportunity that will give the selected candidate(s) the ability to learn about the operations of a mobile network and hands-on experience developing the software systems that form the backbone of our services. > > Mandatory Skills Required: > > 4+ years of Smalltalk Development (Pharo preferred ) > Strong understanding of Linux and databases (MongoDB, MySQL) > Bonus Skills: > > Telecom experience > While a Bachelors degree in Computer Science, Engineering or related is required, relevant experience will be taken into consideration. > > Telna welcomes and encourages applications from people with disabilities. Accommodations are available on request for candidates taking part in all aspects of the selection process. > > Job Type: Full-time > > Experience: > > Smalltalk Development: 4 years (Required) > Pharo development: 4 years (Preferred) > Education: > > Bachelor's (Required) >

May 5, 2018

Re: [Pharo-users] Saving a Smalltalk Project

by Stephan Eggermont

horrido <horrido.hobbies(a)gmail.com> wrote: > What is the best response to this person? Thanks. > Also, this is a project done by Chris Muller. He knows smalltalkers. https://news.squeak.org/2016/05/12/squeak-in-action/ That means the question has a political background. Why not ask him directly? Stephan

May 5, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Thierry Goubier

Le 04/05/2018 Ã 21:13, Denis Kudriashov a Ã©critÂ : > > 2018-05-04 21:10 GMT+03:00 Richard Sargent > <richard.sargent(a)gemtalksystems.com > <mailto:richard.sargent@gemtalksystems.com>>: > > On Fri, May 4, 2018 at 1:04 PM, Denis Kudriashov > <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: > > > 2018-05-04 19:45 GMT+03:00 Sean P. DeNigris > <sean(a)clipperadams.com <mailto:sean@clipperadams.com>>: > > Ramon Leon-5 wrote > > And my point made; I don't even know what that means. > > Ha ha, I googled it and even after seeing the definition > still didn't > understand - we must be getting old ;-) > > Regarding the use of acronyms - while I agree with you as a > general > principle, I wonder about this case. Since the argument IIUC > is that "a > general user won't know the domain well enough to understand > the acronym", > would they understand "abstractSyntaxTree"?! > > > Now I am wonder: is it really correct to call syntax tree as > abstract when it is really implemented? > AST is very known term but now when I read it word by word I > have such questions :). > > > In computer science, an*abstract syntax tree*(AST), or just *syntax > tree*, is a*tree*representation of the*abstract syntactic *structure > of source code written in a programming language. > [Wikipedia] > > > I know it. But my stupid question is why it's still called abstract > while it is implemented for concrete language? This is to make the difference between the parse tree (or concrete syntax tree) and the transformation of that parse tree into an abstract syntax tree (where a bunch of syntax tree nodes created by the parsing are removed or made absent... they are not needed to represent the code structure). Hence the abstract: the abstract syntax tree is an abstraction of the parse tree, even if it represent an exhaustive view of a concrete piece of code. https://web.stanford.edu/class/archive/cs/cs143/cs143.1128/lectures/02/Slid…, slide 159 onward. > That, to me, is as opaque as > the acronym for one not acquainted with the domain, and may > buy us little at > the cost of a good amount of extra typing. Maybe keep the > acronym and add a > good method commentâ¦ > > > > ----- > Cheers, > Sean > -- > Sent from: > http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> > > > >

May 5, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Ben Coman

On 5 May 2018 at 02:20, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > On 04/05/2018 13:54, Richard Sargent wrote: > > >> On Fri, May 4, 2018 at 9:45 AM, Sean P. DeNigris <sean(a)clipperadams.com > >> <mailto:sean@clipperadams.com>> wrote: > >> > >> Ramon Leon-5 wrote > >> > And my point made; I don't even know what that means. > Yes. Point made ;) > >> > >> Ha ha, I googled it and even after seeing the definition still > didn't > >> understand - we must be getting old ;-) > > > Also, if one Googles an acronym, such as the recently cited TMA, one > > gets results like https://en.wikipedia.org/wiki/TMA (a disambiguation > > page with a lengthy list). [I still don't know which TMA was meant, by > > the way, so I can't use it for the following example.] If one Googles > > Abstract Syntax Tree, one will find exactly what it means. But > > additionally, one could make a reasonable guess at an approximation of > > its meaning even without searching. > > > I think that the "we have a TMA situation" is a nice joke if the right > guess is that TMA means "Too Many Acronyms" :) You got it !! cheers -ben

May 5, 2018

[Job] Pharo developers wanted in Toronto

by Ben Coman

On 4 May 2018 at 22:00, <aglynn42(a)gmail.com> wrote: > Telna is looking for developers with Smalltalk experience, preferably > Pharo, in Toronto Canada. > > The role is listed on indeed.ca if anyone is interested. > > Andrew Glynn > Thanks Andrew. Because people are generally interested in seeing where Pharo is being used, I think there is value in copying here the whole job post for the mail archives. If we get to the point where there are too many such posts.... actually that would be a great outcome and we can review policy then. Personally I find this usage very interesting... cheers -ben ----- Telna is a global network operator that focuses on providing "out of the box" connectivity to devices, machines, users and manufacturers. We are changing the way networks operator, by focusing on scalable software-defined networks that can be deployed anywhere in the world in minutes rather than years. We are looking for *Software Engineers* to join our network team to design and develop the core tools that drive our "Network as a Service" platform. *Development experience in smalltalk is mandatory.* This is a unique opportunity that will give the selected candidate(s) the ability to learn about the operations of a mobile network and hands-on experience developing the software systems that form the backbone of our services. *Mandatory Skills Required:* - *4+ years* of Smalltalk Development (Pharo preferred ) - Strong understanding of Linux and databases (MongoDB, MySQL) *Bonus Skills:* - Telecom experience While a *Bachelors degree in Computer Science, Engineering* or related is required, relevant experience will be taken into consideration. Telna welcomes and encourages applications from people with disabilities. Accommodations are available on request for candidates taking part in all aspects of the selection process. Job Type: Full-time Experience: - Smalltalk Development: 4 years (Required) - Pharo development: 4 years (Preferred) Education: - Bachelor's (Required)

May 5, 2018

Re: [Pharo-users] #ast vs. #parseTree

by aglynn42＠gmail.com

Just as TLA is a three letter acronym ... ð -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Esteban A. Maringolo Sent: Friday, May 4, 2018 2:21 PM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>; Richard Sargent <richard.sargent(a)gemtalksystems.com> Subject: Re: [Pharo-users] #ast vs. #parseTree On 04/05/2018 13:54, Richard Sargent wrote: >> On Fri, May 4, 2018 at 9:45 AM, Sean P. DeNigris >> <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: >> >> Ramon Leon-5 wrote >> > And my point made; I don't even know what that means. >> >> Ha ha, I googled it and even after seeing the definition still didn't >> understand - we must be getting old ;-) > Also, if one Googles an acronym, such as the recently cited TMA, one > gets results like https://en.wikipedia.org/wiki/TMA (a disambiguation > page with a lengthy list). [I still don't know which TMA was meant, by > the way, so I can't use it for the following example.] If one Googles > Abstract Syntax Tree, one will find exactly what it means. But > additionally, one could make a reasonable guess at an approximation of > its meaning even without searching. I think that the "we have a TMA situation" is a nice joke if the right guess is that TMA means "Too Many Acronyms" :) Regards! -- Esteban A. Maringolo

May 4, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Denis Kudriashov

2018-05-04 21:10 GMT+03:00 Richard Sargent < richard.sargent(a)gemtalksystems.com>: > On Fri, May 4, 2018 at 1:04 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> >> 2018-05-04 19:45 GMT+03:00 Sean P. DeNigris <sean(a)clipperadams.com>: >> >>> Ramon Leon-5 wrote >>> > And my point made; I don't even know what that means. >>> >>> Ha ha, I googled it and even after seeing the definition still didn't >>> understand - we must be getting old ;-) >>> >>> Regarding the use of acronyms - while I agree with you as a general >>> principle, I wonder about this case. Since the argument IIUC is that "a >>> general user won't know the domain well enough to understand the >>> acronym", >>> would they understand "abstractSyntaxTree"?! >> >> >> Now I am wonder: is it really correct to call syntax tree as abstract >> when it is really implemented? >> AST is very known term but now when I read it word by word I have such >> questions :). >> > > In computer science, an *abstract syntax tree* (AST), or just *syntax > tree*, is a *tree* representation of the *abstract syntactic *structure > of source code written in a programming language. > [Wikipedia] > I know it. But my stupid question is why it's still called abstract while it is implemented for concrete language? > > >> >> >>> That, to me, is as opaque as >>> the acronym for one not acquainted with the domain, and may buy us >>> little at >>> the cost of a good amount of extra typing. Maybe keep the acronym and >>> add a >>> good method commentâ¦ >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> >> >

May 4, 2018