[Pharo-project] Pharo changing the game

Stéphane Ducasse stephane.ducasse at inria.fr
Fri Feb 12 04:30:33 EST 2010

another point, what about automatic initialize?
At one point in the past VW (eliot) was really for introducing it in VW since it would not cost
anything in presence of the JIT. 
Dolphin people did it on Model but they told me that if they could they would remove it.
and this is a really important change to lower the entry level and burden of newcomers.

Now because of "compatibility" we have to code without it for me this is a drawback.

Do we imagine Seaside could have been invented by  VisualAge Smalltalkers (no punt intended)?
No because there is no thisContext!!!

My point is what is the price to pay to compatibility.


On Feb 12, 2010, at 8:02 AM, Lukas Renggli wrote:

>> So yeah, if you're writing a counter application that's probably
>> portable. But as soon as you start to do Pier or Magritte you can write
>> your own portability classes for everything that Seaside does not need.
>> If you're doing a Pier addon like AudioScrobbler or TopFeeder you're
>> almost guaranteed that it's not portable. Believe when I say I speak
>> from experience and it's really frustrating.
> For the average Smalltalk user the ANSI standard does not matter much.
> It only matters for those that want to be able to port libraries
> between Smalltalk dialects. I think making portability as easy as
> possible should be a major focus of all Smalltalk dialects. There are
> simply not enough good libraries available in any Smalltalk
> implementation.
> Lukas
> -- 
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

More information about the Pharo-dev mailing list