On Sun, 15 Nov 2009, Randal L. Schwartz wrote:

>>>>>> "Chris" == Chris Cunnington <smalltalktelevision at gmail.com> writes:
>
> Chris> It's clear to me from things Julian Fitzel has said that the Seaside
> Chris> maintainers will not be porting to Squeak. They plan to develop for
> Chris> Pharo exclusively.
>
> I don't think you're reading that the same way I read it.  I think they're
> saying that while they aren't intentionally breaking it for Squeak core, they
> also won't have anyone serving as the "canary in the coal mine" to see if it
> has broken.
>
> And so far, it hasn't.  3.0 works just fine on Squeak-trunk.  I actually think
> that anything that Seaside breaks can be fixed by making Squeak-trunk support
> what Pharo has.  Ultimately, there shouldn't need to be a different layer for

According to the seaside website, squeak is not supported anymore:
http://www.seaside.st/download/squeak

Seaside 3.0 works in trunk, but not for long:
http://code.google.com/p/pharo/issues/detail?id=331

I'm sure that squeak won't have all the changes that pharo has, and pharo 
won't have all the changes that squeak has, even at the lowest level.

> "Squeak Compat" vs "Pharo Compat".  Squeak *is* Pharo.  Pharo *is* Squeak.
> They just have redundant dev teams. :)

They are similar but have different directions, different goals and the 
gap between them is getting wider every day.


Levente

>
> -- 
> Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
> <merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
> See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
>
>