- Pharo-dev - lists.pharo.org

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

by Sven Van Caekenberghe

> On 30 Dec 2014, at 12:39, Hilaire <hilaire(a)drgeo.eu> wrote: > > 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." Ah, cool. Sorry about the misinterpretation. > 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

Re: [Pharo-dev] The Smalltalk Renaissance Program

by horrido

Which is why I've chosen Pharo as the public "face" of Smalltalk. It has the most active community, and the best chance of widespread adoption. Still, to call it a "new language", to say that "it's not Smalltalk", is a mistake. -- View this message in context: http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797374.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 13:28, "horrido" <horrido.hobbies(a)gmail.com> a Ã©crit : > > > > Pharo is not Smalltalk, but inspired by Smalltalk. > > On Pharo being a "new language"... > > I presume you mean that Pharo will have additional new features and syntax > that extend Smalltalk, making it a /superset/ of Smalltalk rather than just > another /dialect/. I would be very cautious about doing this. > > One of the most desirable qualities of the Smalltalk /language/ is its pure > simplicity. This is one of the things that the Xerox PARC team got > absolutely correct. *You change this at your own peril.* > > If, on the other hand, you mean that the Pharo /environment/ (including the > tooling and class libraries) will evolve and grow and improve, then you > can't really call Pharo a "new language." Do not conflate the two things. > > From "Alien": > > ASH: You still don't understand what you're dealing with, do you? Perfect > organism. Its structural perfection is matched only by its hostility. > LAMBERT: You admire it. > ASH: I admire its purity. A survivor...unclouded by conscience, remorse, or > delusions of morality. > > Generalissimo > > Some features: - Slots - Opal compiler - Enhanced collections - Removal of a lot of old craft - Nativeboost - TxText - GToolkit - Better infrastructure - Command line handlers - JSON support One may argue that these are extensions. But to me there are what makes it different and powerful. I am using VW PUL at times but I prefer Pharo by far when it comes to the development experience. Pharo also allows one to master from the metal up to the UI. Not many contenders on that front. As a software engineer, it matters to me. I hate black magic happening. With Pharo I can make sense of things. I do feel empowered when using Pharo. Not so with other languages and tools where I feel like a user not a (co)-owner. There is this irrational inner joy associated with elegance. I feel it. I like it. It is what makes me choose it over more mainstream tech. We 'll see how far this will lead me and my business. Choosing something is saying no to other things as there is only so much time available. Mastery takes time and dedication. So be it. Phil > > -- > View this message in context: http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797368.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Dec. 30, 2014

Re: [Pharo-dev] The Smalltalk Renaissance Program

by Marcus Denker

> On 30 Dec 2014, at 13:27, horrido <horrido.hobbies(a)gmail.com> wrote: > > >> Pharo is not Smalltalk, but inspired by Smalltalk. > > On Pharo being a "new language"... > > I presume you mean that Pharo will have additional new features and syntax > that extend Smalltalk, making it a /superset/ of Smalltalk rather than just > another /dialect/. I would be very cautious about doing this. > > One of the most desirable qualities of the Smalltalk /language/ is its pure > simplicity. This is one of the things that the Xerox PARC team got > absolutely correct. *You change this at your own peril.* > > If, on the other hand, you mean that the Pharo /environment/ (including the > tooling and class libraries) will evolve and grow and improve, then you > can't really call Pharo a "new language." Do not conflate the two things. > You have no idea what you are talking about. > From "Alien": > > ASH: You still don't understand what you're dealing with, do you? Perfect > organism. Its structural perfection is matched only by its hostility. > LAMBERT: You admire it. > ASH: I admire its purity. A survivor...unclouded by conscience, remorse, or > delusions of morality. > \ I would advise you to not waste everyones time. Please start DOING, stop TALKING. Keep in mind that you have until now not done *anything at all*, yet you know exactly what everyone else is supposed to be doing. Marcus

Dec. 30, 2014

Re: [Pharo-dev] The Smalltalk Renaissance Program

by horrido

> Pharo is not Smalltalk, but inspired by Smalltalk. On Pharo being a "new language"... I presume you mean that Pharo will have additional new features and syntax that extend Smalltalk, making it a /superset/ of Smalltalk rather than just another /dialect/. I would be very cautious about doing this. One of the most desirable qualities of the Smalltalk /language/ is its pure simplicity. This is one of the things that the Xerox PARC team got absolutely correct. *You change this at your own peril.* If, on the other hand, you mean that the Pharo /environment/ (including the tooling and class libraries) will evolve and grow and improve, then you can't really call Pharo a "new language." Do not conflate the two things. >From "Alien": ASH: You still don't understand what you're dealing with, do you? Perfect organism. Its structural perfection is matched only by its hostility. LAMBERT: You admire it. ASH: I admire its purity. A survivor...unclouded by conscience, remorse, or delusions of morality. Generalissimo -- View this message in context: http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797368.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 30, 2014

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