On Jan 2, 2012, at 11:08 AM, Lukas Renggli wrote:
>> please read this mail until the end before replying :)
>
> Done.
>
>>> Moreover, every generic framework included with the core will sooner
>>> or later introduce dependencies from random core packages.
>>
>> Why do you say random. Of course people make mistakes and are not perfect.
>> But we will fix it.
>
> I am saying "random" because people (including me) will start to use
> whatever the auto-completion is offering. And we all know that the
> proposals of the auto-completion are rather random at times. You can
> see that in Pharo, Seaside, Pier, Magritte, ... over time packages
> tend to blend. Whatever you add now, you cannot easily remove
> tomorrow.
I know. This is why I worked on bootstrap during holidays and cleaning event.
>> You see I read and spent time to answer your kind of mail. Because you are
>> still my friend
>> and because I had a lot of fun with you and I'm sure that you could have fun
>> with us.
>
> Thank you.
>
> Now this makes me wonder how I should behave if I am not allowed to
> say why I think that Pharo is on the wrong track?
say it! we are not against this kind of feedback. You know well that I hate
politically correctness.
But think positive.
For example for Announcement:
- raise the issue
- motivate the point
- send code
I'm 100% sure that igor will value your code and criticisms. We are all
for improving but not for bad words
and the system will get better.
We are not autists and we value feedback even when it is negative. We
listen what you are saying believe me.
> You want me to shut up
no just use other words. Yesterday I was in a library reading books on positive
communication and
I'm sure that we can all improve, me the first :).
> and fork from Pharo 1.3? I guess this is only
> way, because with the inclusion of RB into Pharo 1.4 people that want
> to use the original version and everything that depends on it (maybe
> this is just me?) are locked out.
Not totally true :). I could merge the code each time you publish a new version
but this is tedious.
So how do we collaborate? :).
First I will update the RB version.
You see it works with zinc and zinc is even more central because sometimes I
cannot update the system anymore :).
But I would not do that for RB.
We can unload RB from 1.4 without problem but I would like to have a
- calm
- non conflictual
- reasonable
- with clear argument (because I checked the BrowserEnvironment new
location and I imagine that plugin an environment
instead is not something that is done in 15 min)
roadmap
so that WE (YOU and US) can build a roadmap together.
I do not think it is much. I'm even ready to be calm :)
>
> Lukas
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>
