April 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: Company using Pharo [was: Have started an independent developer activity]

by laurent laffont

Thanks Thierry ! ---------- Forwarded message ---------- From: Gmail perso <zebourk(a)gmail.com> Date: Mon, Apr 11, 2011 at 10:38 AM Subject: Re: [Pharo-project] Have started an independent developer activity - Thank you To: laurent laffont <laurent.laffont(a)gmail.com> Of course! You can add Alsim (http://ww.alsim.com/) to the list of company using Pharo. For the details, we are still in early stage of adoption, but it is really promising. As the best way to learn is to practice, we have started the development of a tool for our stock management, as the model is quite simple. The aim is to learn, and to validate some concepts too, like the use of a web interface. So we use: * Pharo * Seaside for the web part * Magma for the data persistence. For the moment, it is still in early stage of development, but it is growing quite fast. I think I will be able to give you more feed back soon. -- Thierry On lundi 11 avril 2011 at 09:52, laurent laffont wrote: On Sun, Apr 10, 2011 at 10:01 PM, ZeBourk <zebourk(a)gmail.com> wrote: Congratulations Laurent! And thank you for having given me the motivation to dive into smalltalk. Now I have introduced it in the company I work for, and it's really fun. Cool ! Can we add it to http://www.pharo-project.org/about/success-stories ? Laurent I wish you success, too. Thierry 2011/4/9 laurent laffont <laurent.laffont(a)gmail.com>: > Hi, > I discovered Smalltalk and Pharo almost three years ago and just after read > Chad Fowler book "Passionate Programmer" (1st edition title was "My job went > to India"). These have changed my developer life, how I perceive software > and that great technology is fun, people doing it more. You're a cool > community and I'm proud to be there. > Now I've started an aside (paid :) independent developer activity thanks to > a cool guy. That would not be possible without all the stuff I learn every > day from the community and the urge to continue you give me. > Each time I've made a step forward (open a blog, write ProfStef, fix bugs, > create PharoCasts) I've been amazed that the generated effects were those > described in Passionate Programmer (go read it !) The last chapter is "Go > independent" so now I need the sequel ;) > Special big thank you to StÃ©phane Ducasse - you're crazy :) Long live Pharo > ! > > PS: nice piece of Passionate Programmer: > When I was in India weeding through hundreds of candidates for only > tens of jobs, the interview team was exhausting itself and running out > of time because of a poor interview-to-hire hit rate. Heads hurting and > eyes red, we held a late-night meeting to discuss a strategic change in the > way we would go through the candidates. We had to either optimize the > process so we could interview more people or somehow interview better > people (or both). With what little was left of my voice after twelve > straight > hours of trying to drag answers out of dumbstruck programmers, I argued > for adding Smalltalk to the list of keywords our headhunters were using > to search their rÃ©sumÃ© database. But, nobody knows Smalltalk in India, cried > the human resources director. That was my point. Nobody knew it, and > programming in Smalltalk was a fundamentally different experience than > programming in Java. The varying experience would give candidates a > different level of expectations, and the dynamic nature of the Smalltalk > environment would reshape the way a Java programmer would approach > a problem. My hope was that these factors would encourage a level of > technical maturity that I hadnât been seeing from the candidates Iâd met so > far. > The addition of Smalltalk to the requirements list yielded a candidate pool > that was tiny in contrast to our previous list. These people were diamonds > in the rough. They really understood object-oriented programming. They > were aware that Java isnât the idealistic panacea itâs sometimes made out > to be. Many of them loved to program! Where have you been for the past two > weeks? we thought. > Unfortunately, our ability to attract these developers for the salaries we > were able to pay was limited. They were calling the shots, and most of > them chose to stay where they were or to keep looking for a new job. > Though we failed to recruit many of them, we learned a valuable recruit- > ing lesson: we were more likely to extend offers to candidates with diverse > (and even unorthodox) experience than to those whose experiences were > homogenous. My explanation is that either the good people seek out > diversity, because they love to learn new things, or being forced into alien > experiences and environments created more mature, well-rounded soft- > ware developers. I suspect itâs a little of both, but regardless of why it > works, we learned that it works. I still use this technique when looking > for developers. > > Laurent Laffont - @lolgzs > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > Developer group: http://cara74.seasidehosting.st > >

April 11, 2011

Re: [Pharo-project] Issue 3931 in pharo: Move all Exceptions-Kernel to Kernel-Exceptions

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #2 on issue 3931 by marcus.d...(a)gmail.com: Move all Exceptions-Kernel to Kernel-Exceptions http://code.google.com/p/pharo/issues/detail?id=3931 in 13140

April 11, 2011

Re: [Pharo-project] Issue 3977 in pharo: Undeclared vars in MorphTreeMorph

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3977 by marcus.d...(a)gmail.com: Undeclared vars in MorphTreeMorph http://code.google.com/p/pharo/issues/detail?id=3977 in 13140

April 11, 2011

Re: [Pharo-project] Issue 3986 in pharo: Bug with Delay during clock rollover

by pharo＠googlecode.com

Comment #1 on issue 3986 by gazzagu...(a)googlemail.com: Bug with Delay during clock rollover http://code.google.com/p/pharo/issues/detail?id=3986 (file attached, failed first time!) Attachments: DelayRolloverFix.1.cs 1.3 KB

April 11, 2011

Re: [Pharo-project] Delay bug

by Gary Chambers

Issue http://code.google.com/p/pharo/issues/detail?id=3986 Regards, Gary ----- Original Message ----- From: "Adrian Lienhard" <adi(a)netstyle.ch> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, April 06, 2011 5:41 PM Subject: Re: [Pharo-project] Delay bug We managed to resolve our initial problem with the process scheduling [1]. All Cmsbox customers have been migrated to Pharo and it works very reliably now. Gary, maybe you could open a ticket already now and post what you know at this time to get early feedback. [1] http://code.google.com/p/pharo/issues/detail?id=3498 Cheers Adrian On Apr 6, 2011, at 18:24 , StÃ©phane Ducasse wrote: > thanks gary. > Yes adrian got a problem on his server after two weeks of load. I do not > know how we can improve them. > > Stef > > On Apr 6, 2011, at 6:02 PM, Gary Chambers wrote: > >> Well, we have been having problems with applications appearing to hang >> every 6 days or so (sound familiar?). >> >> I have identified a bug in the Delay implementation, rather obscure, but >> highlighted by our applications that make HEAVY use of processes/(tight, >> a few tens of milliseconds)delays/semaphores etc. >> Naturally due to an edge case on millisecond clock rollover... >> >> Affects all Squeak/Pharo versions, as far as I can tell. (It is separate >> from the OSProcess issues I have posted about a few weeks ago). >> >> I've developed a potential fix, though I'll have to let you all know >> whether (hopefully) successful in a week or two... fingers crossed! >> >> I hope it is fixable, last hurdle for business applications, from our >> point of view. >> >> I'll post details when fix confirmed or failed then. >> >> Regards, Gary > >

April 11, 2011

[Pharo-project] Issue 3986 in pharo: Bug with Delay during clock rollover

by pharo＠googlecode.com

Status: FixProposed Owner: gazzagu...(a)googlemail.com CC: adrian.l...(a)gmail.com, marcus.d...(a)gmail.com Labels: Type-ReportDefect New issue 3986 by gazzagu...(a)googlemail.com: Bug with Delay during clock rollover http://code.google.com/p/pharo/issues/detail?id=3986 I have identified a bug with Delays that are scheduled close to the millisecond clock rollover that can occur when other delays expire around the same time. The issue appears to be that when scheduling a delay, the resumption time gets set and, before the AccessProtect critical block can be entered, the TimingSemaphore gets signalled, causing the timer process to handle an expired delay. If the clock rolls over before the resumption of the process that was scheduling the original delay, that delay gets scheduled with the resumption time that was determined prior to the clock rollover, hence a delay of around 6 days. A fix is proposed in the attached change set, tested empirically during a rollover with the result of no "rogue" delays - not conclusive but in our production code it appears the problem is resolved. Regards, Gary

April 11, 2011

[Pharo-project] Brussels Sprint: gathering number of attendes

by Johan Brichau

Hi everyone. To make sure we have enough food and drinks for everyone. Please make sure to let us know you are coming. >From previous emails, I have understood the following people are attending: - Steph - Marcus - Sven - Mariano - Craig Latta - Thomas Holzer - Andy - Johan Someone on here who is not attending? Someone not attending who is listed above? The parking access code will follow shortly. ps: I will bring some Faro beer this time then ;-) Johan

April 11, 2011

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

by pharo＠googlecode.com

Comment #3 on issue 3982 by marianopeck: Error: can''t find EOCD position http://code.google.com/p/pharo/issues/detail?id=3982 Yes, that would be nice. We have already seen this problem FAR so many times.

April 11, 2011

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

by pharo＠googlecode.com

Comment #2 on issue 3982 by nicolas....(a)gmail.com: Error: can''t find EOCD position http://code.google.com/p/pharo/issues/detail?id=3982 Couldn't the exception be handled with an automated or manual action via a more appropriated dialog like: Error can't find EOCD blah blah The package appear to be corrupted, maybe due to a communication error What would you like to do ? - flush the cache and retry - abort operation

April 11, 2011

[Pharo-project] Issue 3985 in pharo: Create temporary in debugger does not work for new keyword method

by pharo＠googlecode.com

Status: Accepted Owner: laurent....(a)gmail.com New issue 3985 by laurent....(a)gmail.com: Create temporary in debugger does not work for new keyword method http://code.google.com/p/pharo/issues/detail?id=3985 Reproductible in Pharo 1.2 (Full) - looks ok in PharoCore 1.3 Create a class in the browser like Foo >> bar self doSomethingWith: 2. save and evaluate Foo new bar. Debugger pops up. Click create method doSomethingWith: Foo>>doSomethingWith: aSmallInteger a := aSmallInteger ^ a. Accept. Dialog popus up, select declare temp => does not work.

April 11, 2011