<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><div><span style="color:rgb(34,34,34)">I like the Announcements route. SystemChangeNotifier is a dog. Compatibility with Pharo is in the long-term very important </span></div>
</div></div></div></div></blockquote><div><br></div><div><div>Freedom from Pharo constraints is even more important.</div><div><br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><div><span style="color:rgb(34,34,34)">(but it has to be a two-way street, and not blind).</span></div></div></div></div></div></blockquote>
<div><br></div><div>I don't believe Pharo will ever be interested in a two-way street of compatibility with Squeak. If anything, the opposite. Neither group is interested in feeling constrained by the other. The Pharo fork happened for good reasons.<br>
</div><div><br></div><div>We should pursue our own wildest imaginations, not follow Pharo. We should steal components of Pharo which offer the kind of functional leverage ratio's appropriate for Squeak.</div><div><br>
</div><div>PS -- None of the above should imply I'm against Announcements. I know nothing about it other than its Listener Pattern le Grande. Hopefully not too heavyweight..</div><div><br></div></div></div></div>