Logging from the Compiler

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Logging from the Compiler

Frank Shearar-3
On 12 Dec 2013, at 20:44, Chris Muller <[hidden email]> wrote:

> On Thu, Dec 12, 2013 at 2:22 PM, Frank Shearar <[hidden email]> wrote:
>> On 12 December 2013 19:43, Chris Muller <[hidden email]> wrote:
>>>> I like the Announcements route.  SystemChangeNotifier is a dog.
>>>> Compatibility with Pharo is in the long-term very important
>>>
>>>
>>> Freedom from Pharo constraints is even more important.
>>>
>>>> (but it has to be a two-way street, and not blind).
>>>
>>>
>>> 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.
>>>
>>> We should pursue our own wildest imaginations, not follow Pharo.
>>
>> No arguments, but...
>>
>>> We should
>>> steal components of Pharo which offer the kind of functional leverage
>>> ratio's appropriate for Squeak.
>>
>> ... you can't do that without some kind of compatibility. Not without
>> entirely rewriting stuff, which is kind've missing the point of
>> stealing.
>
> Not rewriting, porting.  Which doesn't lose the value of stealing.

Ah but the epsilon between rewriting and porting tends to zero as the two systems diverge.

frank
Reply | Threaded
Open this post in threaded view
|

Re: Logging from the Compiler

Eliot Miranda-2



On Fri, Dec 13, 2013 at 12:41 AM, Frank Shearar <[hidden email]> wrote:
On 12 Dec 2013, at 20:44, Chris Muller <[hidden email]> wrote:

> On Thu, Dec 12, 2013 at 2:22 PM, Frank Shearar <[hidden email]> wrote:
>> On 12 December 2013 19:43, Chris Muller <[hidden email]> wrote:
>>>> I like the Announcements route.  SystemChangeNotifier is a dog.
>>>> Compatibility with Pharo is in the long-term very important
>>>
>>>
>>> Freedom from Pharo constraints is even more important.
>>>
>>>> (but it has to be a two-way street, and not blind).
>>>
>>>
>>> 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.
>>>
>>> We should pursue our own wildest imaginations, not follow Pharo.
>>
>> No arguments, but...
>>
>>> We should
>>> steal components of Pharo which offer the kind of functional leverage
>>> ratio's appropriate for Squeak.
>>
>> ... you can't do that without some kind of compatibility. Not without
>> entirely rewriting stuff, which is kind've missing the point of
>> stealing.
>
> Not rewriting, porting.  Which doesn't lose the value of stealing.

Ah but the epsilon between rewriting and porting tends to zero as the two systems diverge.

+1
--
best,
Eliot


12