Phil

2012/9/7 St�phane Ducasse <stephane.ducasse@inria.fr>

Yes !

>> Pharo manifesto
>> - Better for the better
>> - Beauty to learn from
>> - Not backward compatible ***
>> - Clean, lean and fast
>>
>
> Every wtf we leave in the system limits the human expression of ourselves
> and our users. For one thing, aesthetics count. Emotions are hugely
> important to the quality of one's work, and unless we are all inspired by a
> beautiful system, our discontent will be reflected in code written in and on
> top of Pharo. Also, while crusty old Pharo wizards may know where all these
> little land mines are that must be avoided, new users may waste hours/days
> before finding out that things don't work the way one would naturally expect
> them too.
>
> If we can operate on RPackage in a live system, breaking code committing and
> loading, we can change *anything*. I've definitely felt the pain in 2.0, but
> this is what we're working for. Let's rip the bandaid off and have the
> system of our dreams. If anything, I believe the question should *never* be
> "do we leave this crap in the system or not?", but merely "how do we ease
> the pain of making this better?", whether via deprecations, RB
> transformations, or whatever; and we seem to be making steady progress on
> that front.
>
>
>
> --
> View this message in context: http://forum.world.st/Who-broke-UTF8TextConverter-tp4645473p4646399.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>