<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I first used Squeak 1.x and the system browse was enough for me to discover the system. Modern Pharo scares me though. The tools haven't scaled.</div><div id="AppleMailSignature">Russell</div><div id="AppleMailSignature"><br>Sent from my phone<div><br></div></div><div><br>On 23 Jul 2016, at 2:06 PM, 'Jason Grossman' <a href="mailto:spam-me@xeny.net">spam-me@xeny.net</a> [self-interest] <<a href="mailto:self-interest@yahoogroups.com">self-interest@yahoogroups.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<span style="display:none"> </span>
<div id="ygrp-text">
<p>Yes, excellent.<br>
<br>
And then there's also stuff that's even more high level than that.<br>
<br>
For example, when I look through the object systems of Pharo or even the <br>
relatively small Io, I find a mixture of things that are intended for <br>
widespread use and things that are intended for niche uses, for lots of <br>
reasons (e.g. they're experimental, or they're optimised for only <br>
certain cases, or they're badly optimised but get correct results in <br>
corner cases, or they can talk to other obsolete systems, or ...). This <br>
can be shown in the internal documentation of the objects and sometime <br>
is (not always - grrr), but that's not where it's most useful, is it? I <br>
want to know before I start exploring which objects I should consider <br>
first.<br>
<br>
On 23 Jul 2016, at 14:01, David Ungar <a href="mailto:ungar@me.com">ungar@me.com</a> [self-interest] <br>
wrote:<br>
<br>
> Sure, no argument there. Someone had written about parameter type <br>
> comments. Self objects and slots can have comments in their <br>
> annotations. Easy enough to write some reflective code to compile it, <br>
> search it, etc.<br>
</p>
</div>
<!-- end group email -->
</div></blockquote></body></html>