[squeak-dev] Re: [Election] Candidate list with 11 candidates is final, 6 days until election starts!

Miguel Enrique Cobá Martinez miguel.coba at gmail.com
Fri Mar 5 15:44:57 UTC 2010

El vie, 05-03-2010 a las 12:45 +0100, Michael Haupt escribió:
> Germán,
> since interoperability was on my list, here's an attempt ... :-)
> On Fri, Mar 5, 2010 at 12:13 PM, Germán Arduino <garduino at gmail.com> wrote:
> > What would happen if at some point such frameworks start not working on
> > Squeak? You (insert the candidate name here) think that Squeak Board/community
> > should do anything about it or it is a responsibility of the authors
> > of the framework?
> Regarding the role of the board, I refer to the politician thing again
> that was raised numerous times in that other thread. ;-)
> The board should care about these things in my opinion. So how does
> taking care look? Shaping and fostering an infrastructure that allows
> for interoperability / applicability of packages and frameworks across
> systems. That is,
> * find which compatibility layers (like Grease, which Nicolas mentioned) exist,
> * devote special attention to them by writing tests tests tests in all
> available systems and frequently run them,
> * encourage developers to actually use such compatibility layers by
> keeping them up to date.
> Actual developers will have to do something as well, obviously.
> About the community: it should come to a conclusion whether there is
> actual *interest* in having a package available across system
> boundaries. Would the Pharo community like to include Etoys? I doubt
> it, so the Pharo community will have little incentive to drive
> interoperability in this particular regard.

I disagree, the problem with etoys is that is (was) not maintained in
Squeak, it was old, it impregnated everything and is wrongly was posed
as the reason for Squeak to exist. Pharo is more akin to the idea of a
development platform, not only web development, but a general
development platform. So if Seaside, Magritte, Etoys or whatever is
loadable in a core/dev Pharo image, the Pharo guys happily use it.
It is just that we don't want to have it in the core image. For us is
just a package that you can load in Pharo (when Etoys is a real laodable
plackage) and use it if you need it. Isn't nothing different as Seaside
for someone that don't give a dime for Seaside. If it can be loaded
good, if isn't part of the core image, better yet.


> Best,
> Michael

Miguel Cobá

More information about the Squeak-dev mailing list