2012/12/11 Chris Muller <[email protected]>:
> If my goal is to make my computer work for ME, then I want my
> development system to maximize my leverage and minimize my effort.
> Breaking compatibility for cleaner code subverts this, as Hannes said,
>

One thing is clear, forking is not anything near minimizing the
effort, quite the opposite.
It's the way to build one's own jail  - some will say to be free ;).
Clearly, Marcus and Stephane have other goals and it's a good thing to
have both Squeak and Pharo.

>>> Constant input in maintenance effort is needed.
>
> I want to use my time applying Smalltalk to real-world problems, not
> API changes.
>
> A blue-plane innovation is worth breaking backward compatibility,
> reinventing the past isn't.
>

Ah, if future is the past, then I wonder whether it's not yet another
damned Smalltalk circularity trick ;)

>
>>> maintaining libraries and maybe compatibility layers are very welcome.
>>>
>> Yes, and how did we ever thought we could invent the future with Squeak
>> when in reality, we could not even change a typo in a comment?
>>
>>         Marcus
>>
>>
>>
>>
>

Reply via email to