<div dir="ltr">Another path is to contribute to Pharo, you know the best way to predict the future etc...<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/12 Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 12 December 2013 19:43, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
>> I like the Announcements route. SystemChangeNotifier is a dog.<br>
>> Compatibility with Pharo is in the long-term very important<br>
><br>
><br>
> Freedom from Pharo constraints is even more important.<br>
><br>
>> (but it has to be a two-way street, and not blind).<br>
><br>
><br>
> I don't believe Pharo will ever be interested in a two-way street of<br>
> compatibility with Squeak. If anything, the opposite. Neither group is<br>
> interested in feeling constrained by the other. The Pharo fork happened for<br>
> good reasons.<br>
><br>
> We should pursue our own wildest imaginations, not follow Pharo.<br>
<br>
</div>No arguments, but...<br>
<div class="im"><br>
> We should<br>
> steal components of Pharo which offer the kind of functional leverage<br>
> ratio's appropriate for Squeak.<br>
<br>
</div>... you can't do that without some kind of compatibility. Not without<br>
entirely rewriting stuff, which is kind've missing the point of<br>
stealing.<br>
<span class="HOEnZb"><font color="#888888"><br>
frank<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> PS -- None of the above should imply I'm against Announcements. I know<br>
> nothing about it other than its Listener Pattern le Grande. Hopefully not<br>
> too heavyweight..<br>
><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>