Users don't know the details and they don't care. If they open a Pharo
image and its slow, then this just gives a bad impression. If people
start telling each other "Pharo is slow", we will loose reputation
that is very hard to win back.

+9999999999999999999999999999

I recommend Pharo to a lot of people that was using Squeak and this is the first thing they told me and the first thing that happens. It doesn't matter how many fixes you did, or closures or traits. If you open a browser and takes 1 seconds. You close it. You even don't see all of the real features. And as Andrian says, they doesn't know why it is slow, or how to have a faster Pharo . They don't know what to remove or whateever.

Please, we are loosing gays for this topic.

�

So I suggest to either disable the features that make the browser slow
so that it is snappy again or to replace it with the version Lukas is
using until it is fast enough.

As I said, +999999999999999999999
�

Cheers,
Adrian

On Jul 14, 2009, at 11:49 , Michael Rueger wrote:

> On Tue, Jul 14, 2009 at 11:47 AM, St�phane
> Ducasse<stephane.ducasse@inria.fr> wrote:
>> take the core image.
>> The default tools in web dev are too slow right now.
>
> Maybe we should point that out somewhere as we promote the dev-images
> as being "Pharo"?
> As we can see from some of the discussion on the Squeak list people
> then think Pharo in general is dog slow...
>
> Michael
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project