December 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Can MongoTalk execute plan javascript MongoDB queries?

by Norbert Hartl

> Am 30.12.2014 um 02:32 schrieb Sebastian Sastre <sebastian(a)flowingconcept.com>: > > Is anybody here using MongoTalk doing some fancy custom queries? Not just with boolean conditions but with regex for example. > > Iâm interested in being able to execute and get the results of a raw javascript query but I cannot found how to do it. > > I am missing something? In order to execute a javascript query you would need a javascript interpreter. As this is not feasible Mongo provides alternative constructs for the most important things you need. For the regex it would be aMongoCollection select: { 'fieldName' -> { '$regex' -> '.*foo' } asDictionary } asDictionary Hope that helps, Norbert

Dec. 30, 2014

Can a hash be negative ?

by ClÃ©ment Bera

Hello Pharoers, I was wondering, is it a good practice to have negative hashes ? Based on the class comment of Object>>#hash *"Answer a SmallInteger whose value is related to the receiver's identity. [...]"* The hash is a smallInteger and therefore can be negative. Thanks for any answer. Clement

Dec. 30, 2014

Re: [Pharo-dev] A toast

by Hilaire

Thanks to all of you for this wonderful perspectives. Hilaire Le 29/12/2014 13:59, Esteban Lorenzano a Ã©crit : > Hello Pharoers, > > (sorry for the long post) > > I'm on holidays so I've been silent this latests days, but I didn't want to let the opportunity goes to propose a toast :) -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Dec. 30, 2014

Re: [Pharo-dev] What do you call someone who writes Pharo code?

by Hilaire

Le 29/12/2014 13:40, Sven Van Caekenberghe a Ã©crit : > Hilaire, > >> On 29 Dec 2014, at 12:21, Hilaire <hilaire(a)drgeo.eu> wrote: >> >> Le 28/12/2014 21:04, phil(a)highoctane.be a Ã©crit : >>> >>> Jokes aside, Pharo is solid for commercial work. >>> >> >> It is crazy how it seems so successful in this particular area. > > I have a hard time interpreting this remark as positive. I think one should be careful when writing email as my enthusiastic tone was not transported through the wire. It is only mean to be a p-o-s-i-t-i-v-e remark, one can rephrase it as: "It is wonderful to see Pharo successful in the business area because in the long term it can definitely help to sustain the Pharo evolution, maturation and development effort, thanks to the support that such successful business can/could contribute to Pharo, though visibility, financial support or/and source code contribution to Pharo core or external Pharo library package." Hilaire > > Why do you say that is 'crazy' ? > > Why do you say 'seems' ? > > Why do you say 'this particular area' ? > > Sven > > > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Dec. 30, 2014

Fuel and multiple bytecode set support

by ClÃ©ment Bera

Hello, As some of you may know, Pharo is being enhanced with support for multiple bytecode sets. This will allow to run at the same time compiled methods with 2 different bytecode sets for experimentation and to add easily the new bytecode set described in this ESUG paper <http://esug.org/data/ESUG2014/IWST/Papers/iwst2014_A%20bytecode%20set%20for…> . The virtual machine knows which bytecode set the compiled method uses for its encoding based on the sign of its header. This means that on the contrary to right now, a compiled method *can* have a negative header. The issue is that typically operations such as #bitAnd: or #+ to access bits of the smallinteger does not work the same way on negative integers (2 complement's implementation of integers), resulting in incorrect values. I am fixing the problematic cases in Pharo. One case is in Fuel and I can't fix it myself. It's in: FLCompiledMethodCluster>>#serializeInstance: aCompiledMethodToSerialize with: anEncoder "some code" header := aCompiledMethod header. "some code" anEncoder *encodeUint32*: header "some code" This looks problematic because now header is not a uint anymore but a sint. In addition, #encodeUint32: uses #bitAnd: which may work differently on negative integers. What do you fuel experts think ? Is there anything to fix there ? Best, Clement

Dec. 30, 2014

Can MongoTalk execute plan javascript MongoDB queries?

by Sebastian Sastre

Is anybody here using MongoTalk doing some fancy custom queries? Not just with boolean conditions but with regex for example. Iâm interested in being able to execute and get the results of a raw javascript query but I cannot found how to do it. I am missing something?

Dec. 30, 2014

Re: [Pharo-dev] The Smalltalk Renaissance Program

by horrido

>> Smalltalk organizations have focussed too much on /technical merit/, and >> not >> enough on PR and marketing. > > On making money too. You're saying Smalltalk organizations are too focussed on making money? I've heard that, too. It sounds very odd to me. I thought these organizations were created for the love of the language. Am I too naive? > We market Pharo as a new language because Pharo is cool and we do not have > to carry with us the "old" aspects and fight against the museum syndrome. Then you have failed. Virtually every mention of Pharo on the web is directly linked to Smalltalk. In the public consciousness, there is little or no distinction between Pharo and Smalltalk. Trying to force this distinction, I believe, is a mistake; it's futile. If Pharo is a new language disconnected from Smalltalk, then it loses whatever cachet Smalltalk has. Smalltalk already has a ton of references on the web; it just needs to be cleaned up a bit. Hence, Smalltalk Renaissance. Moreover, we can fight the museum syndrome through branding and education. Smalltalk is already a positive marque; it's renown for its influence in language design, for example. Pharo has to start from scratch in building its brand. It's more challenging. So far, it has ridden on Smalltalk's coattails. Continuing on this path is the smarter move. > ESUG is about the community. Without community then it is terrible. We set > up also a program for teachers. Now in the US there is nearly nobody > teaching smalltalk and this is a pity. Smalltalk Renaissance is also about the community, as I've already explained. Yes, getting Smalltalk into US (and Canadian) schools is vitally important. I haven't yet determined SRP's role in this regard. -- View this message in context: http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797336.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 30, 2014

Re: [Pharo-dev] The Smalltalk Renaissance Program

by phil＠highoctane.be

Le 30 dÃ©c. 2014 00:23, "Sebastian Sastre" <sebastian(a)flowingconcept.com> a Ã©crit : > > Iâm a Smalltalker that is happy when JavaScript and LISP and Phyton and Ruby and Dart gain popularity because it makes my life easier when I have to explain to the next dynamic friendly developer how our workspace, inspector and debugger works and how our library gets navigated so the new guy can fell he can master it by himself easier than other tools (which is a Smalltalk language design intention from day zero, and totally successful at it BTW). > > I can understand that some might feel indifferent at Scala or Java popularity but being "a Pharoerâ and hostile, antagonising or actively indifferent to Smalltalk's popularity and branding efforts is a frank strategic parricide And so we entered the land of Zealots of True Faith (tm). PR is useful. But patronizing what is and what is not leaves me cold. Phil > > > > > >> On Dec 29, 2014, at 5:40 PM, horrido <horrido.hobbies(a)gmail.com> wrote: >> >> From "The City on the Edge of Forever": >> >> KIRK: Then what is it? >> GUARDIAN: *A question.* Since before your sun burned hot in space and before >> your race was born, I have awaited a question. >> KIRK: What are you? >> GUARDIAN: I am the Guardian of Forever. >> KIRK: Are you machine or being? >> GUARDIAN: I am both and neither. I am my own beginning, my own ending. >> >> ----- >> >> Clearly, I need to explain myself in greater detail... >> >> The efforts of organizations such as STIC and ESUG are laudable. >> Nevertheless, they have failed to popularize Smalltalk. Today, *Smalltalk is >> a largely forgotten language*. This can be seen at the TIOBE index where >> Smalltalk has literally fallen off a cliff (it used to be on the top 100 >> list, but has since disappeared). At Redmonk and langpop.corger.nl, >> Smalltalk is somewhere around the 65th position! >> >> Smalltalk does not get much developer attention. It doesn't get talked about >> in the press like Dart and JavaScript and Java do. The language is almost >> never on the minds of CEOs and CTOs, the business decision makers. I believe >> I know why. >> >> Smalltalk organizations have focussed too much on /technical merit/, and not >> enough on PR and marketing. Understandable, since engineers are >> /technically-minded/ and not so much into human behaviour. I think we need >> to treat developers and businessmen like consumers. We need to sell >> Smalltalk to them in the same way we sell iPhones and PlayStations. In other >> words, we need to build /hype/. >> >> Let's face it: at the best of times, the subject of Smalltalk is rather >> staid. STIC and ESUG and the Smalltalk Foundation are not likely to change >> this. *I want Smalltalk Renaissance to change this.* >> >> The Smalltalk Renaissance Program is a highly focussed campaign. Like the >> language itself, I want to Keep It Simple. (That's why I'm trying to keep >> the website clean and free of excess baggage.) >> >> The SRP cannot succeed without /your/ involvement, your participation. I am >> not much more than the curator and editor for Smalltalk Renaissance, >> although I'm also formulating the short-term and long-term strategy. (You >> can call me "Generalissimo" Eng. ;-) ) >> >> One of the things I intend to do is ask members of the Smalltalk community >> to submit /fresh/ essays and articles on Smalltalk. I have a list of essay >> topics prepared, carefully chosen for their relevance and impact on the >> future of Smalltalk. I shall be asking people to pick a topic and run with >> it. If there are multiple submissions for a particular topic, I shall choose >> the best one, edit it, and post it on Smalltalk Renaissance. *I guarantee >> you will look good!* >> >> Make no mistake, this is a critical step. *These essays will address the >> concerns of non-Smalltalk developers.* You need to make compelling >> arguments. >> >> Then we promote these articles and essays on Reddit and Hacker News and so >> on. >> >> In the near future, I will also submit Smalltalk articles to the IT press, >> such as Wired and InfoWorld. These articles may well benefit from /your >> contributions/. >> >> Another important piece of the strategy is to obtain corporate sponsorship. >> If not for Apple, the Swift language would never have gotten so much >> mindshare. If not for Google, Go would've failed to gain a significant >> following. If not for Microsoft, C# would've been forgotten. In today's >> highly competitive programming language field, if you don't have a big name >> backer, you're already behind the eight ball. Grass roots are unlikely to >> succeed. >> >> Getting the imprimatur of a major technology company is a PR coup of >> inestimable value. But it's also vital for another reason. In the longer >> term, I want to launch software projects that improve on the Smalltalk >> technology. Projects such as extending the tooling around the Smalltalk >> environment (which has been criticized for not playing well with existing >> file-based tooling). Projects such as improving interoperability with >> existing (Windows-based) infrastructures in the enterprise (which has been a >> source of criticism from the likes of Robert Martin). These projects must be >> financed because open source volunteerism isn't enough, not by a long shot. >> And this is why we need corporate sponsorship. >> >> Before I make a pitch to a CEO, Smalltalk Renaissance must achieve some >> degree of legitimacy. It can do this by signing up well-known names from the >> Smalltalk community. Names such as the late James Robertson or StÃ©phane >> Ducasse. I already have a draft letter prepared for an important CEO. I'm >> only waiting for a list of SRP signatories before firing off the letter. >> (Hint, hint.) >> >> This is what I've come up with so far in my strategic planning. It's a >> work-in-progress. >> >> As for Pharo, I've downloaded it and played with it briefly. As far as I can >> tell, the IDE is not much different from Squeak. Like I said, the design has >> been tweaked and improved, but I don't see anything groundbreaking. Maybe >> you and I have different ideas of what "groundbreaking" means. >> >> Nevertheless, as another poster indicated, we can leave this for the future. >> For the time being, we need to make Smalltalk, and Pharo in particular, more >> attractive to the Enterprise. I'm sure Pharo is doing this. Kudos. >> >> >> >> >> -- >> View this message in context: http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797313.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >

Dec. 30, 2014

Re: [Pharo-dev] The Smalltalk Renaissance Program

by Sebastian Sastre

Iâm a Smalltalker that is happy when JavaScript and LISP and Phyton and Ruby and Dart gain popularity because it makes my life easier when I have to explain to the next dynamic friendly developer how our workspace, inspector and debugger works and how our library gets navigated so the new guy can fell he can master it by himself easier than other tools (which is a Smalltalk language design intention from day zero, and totally successful at it BTW). I can understand that some might feel indifferent at Scala or Java popularity but being "a Pharoerâ and hostile, antagonising or actively indifferent to Smalltalk's popularity and branding efforts is a frank strategic parricide <http://en.wikipedia.org/wiki/Parricide> > On Dec 29, 2014, at 5:40 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > > From "The City on the Edge of Forever": > > KIRK: Then what is it? > GUARDIAN: *A question.* Since before your sun burned hot in space and before > your race was born, I have awaited a question. > KIRK: What are you? > GUARDIAN: I am the Guardian of Forever. > KIRK: Are you machine or being? > GUARDIAN: I am both and neither. I am my own beginning, my own ending. > > ----- > > Clearly, I need to explain myself in greater detail... > > The efforts of organizations such as STIC and ESUG are laudable. > Nevertheless, they have failed to popularize Smalltalk. Today, *Smalltalk is > a largely forgotten language*. This can be seen at the TIOBE index where > Smalltalk has literally fallen off a cliff (it used to be on the top 100 > list, but has since disappeared). At Redmonk and langpop.corger.nl, > Smalltalk is somewhere around the 65th position! > > Smalltalk does not get much developer attention. It doesn't get talked about > in the press like Dart and JavaScript and Java do. The language is almost > never on the minds of CEOs and CTOs, the business decision makers. I believe > I know why. > > Smalltalk organizations have focussed too much on /technical merit/, and not > enough on PR and marketing. Understandable, since engineers are > /technically-minded/ and not so much into human behaviour. I think we need > to treat developers and businessmen like consumers. We need to sell > Smalltalk to them in the same way we sell iPhones and PlayStations. In other > words, we need to build /hype/. > > Let's face it: at the best of times, the subject of Smalltalk is rather > staid. STIC and ESUG and the Smalltalk Foundation are not likely to change > this. *I want Smalltalk Renaissance to change this.* > > The Smalltalk Renaissance Program is a highly focussed campaign. Like the > language itself, I want to Keep It Simple. (That's why I'm trying to keep > the website clean and free of excess baggage.) > > The SRP cannot succeed without /your/ involvement, your participation. I am > not much more than the curator and editor for Smalltalk Renaissance, > although I'm also formulating the short-term and long-term strategy. (You > can call me "Generalissimo" Eng. ;-) ) > > One of the things I intend to do is ask members of the Smalltalk community > to submit /fresh/ essays and articles on Smalltalk. I have a list of essay > topics prepared, carefully chosen for their relevance and impact on the > future of Smalltalk. I shall be asking people to pick a topic and run with > it. If there are multiple submissions for a particular topic, I shall choose > the best one, edit it, and post it on Smalltalk Renaissance. *I guarantee > you will look good!* > > Make no mistake, this is a critical step. *These essays will address the > concerns of non-Smalltalk developers.* You need to make compelling > arguments. > > Then we promote these articles and essays on Reddit and Hacker News and so > on. > > In the near future, I will also submit Smalltalk articles to the IT press, > such as Wired and InfoWorld. These articles may well benefit from /your > contributions/. > > Another important piece of the strategy is to obtain corporate sponsorship. > If not for Apple, the Swift language would never have gotten so much > mindshare. If not for Google, Go would've failed to gain a significant > following. If not for Microsoft, C# would've been forgotten. In today's > highly competitive programming language field, if you don't have a big name > backer, you're already behind the eight ball. Grass roots are unlikely to > succeed. > > Getting the imprimatur of a major technology company is a PR coup of > inestimable value. But it's also vital for another reason. In the longer > term, I want to launch software projects that improve on the Smalltalk > technology. Projects such as extending the tooling around the Smalltalk > environment (which has been criticized for not playing well with existing > file-based tooling). Projects such as improving interoperability with > existing (Windows-based) infrastructures in the enterprise (which has been a > source of criticism from the likes of Robert Martin). These projects must be > financed because open source volunteerism isn't enough, not by a long shot. > And this is why we need corporate sponsorship. > > Before I make a pitch to a CEO, Smalltalk Renaissance must achieve some > degree of legitimacy. It can do this by signing up well-known names from the > Smalltalk community. Names such as the late James Robertson or StÃ©phane > Ducasse. I already have a draft letter prepared for an important CEO. I'm > only waiting for a list of SRP signatories before firing off the letter. > (Hint, hint.) > > This is what I've come up with so far in my strategic planning. It's a > work-in-progress. > > As for Pharo, I've downloaded it and played with it briefly. As far as I can > tell, the IDE is not much different from Squeak. Like I said, the design has > been tweaked and improved, but I don't see anything groundbreaking. Maybe > you and I have different ideas of what "groundbreaking" means. > > Nevertheless, as another poster indicated, we can leave this for the future. > For the time being, we need to make Smalltalk, and Pharo in particular, more > attractive to the Enterprise. I'm sure Pharo is doing this. Kudos. > > > > > -- > View this message in context: http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797313.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Dec. 29, 2014

Re: [Pharo-dev] Jun4Pharo so exciting :)

by Sven Van Caekenberghe

> On 29 Dec 2014, at 23:10, stepharo <stepharo(a)free.fr> wrote: > > Sven > > Jun is a 3D frameworks developed in 1998 in VisualWorks http://aokilab.kyoto-su.ac.jp/jun/index.html > It was quite advanced and this is nice to get more people doing 3d in Pharo. > They are using the back -end developed by ronie and JB and this is cool > > Athens is just a canvas and a oo decomposition of the canvas, brush and strokes > nothing related to 3D. Ah, OK - more choice, more options is good. > Stef > > > Le 29/12/14 20:20, Sven Van Caekenberghe a Ã©crit : >>> On 29 Dec 2014, at 15:36, stepharo <stepharo(a)free.fr> wrote: >>> >>> https://www.youtube.com/watch?v=sH_P5otiWJM&feature=youtu.be >> It certainly looks nice, but what is Jun exactly ? >> >> > >

Dec. 29, 2014