But you never even understood what the reason behind kernel-extension was, you criticised it and refused to use anything that depended on it, because it wasn't perfectly what you wanted, and it contained method overrides.
This was feedback and explanation for YOU of why we did not include it.
That was the whole point, it was supposed to contain method overrides. If you put all of the method overrides for the kernel in one place, then multiple overlapping method overrides from different packages do not occur, there will be no conflicts.
You didn't really participate in that discussion, you simply said things along the line of Kernel-Extensions includes Null therefore we dont like it, full stop.
No I gave you feedback. Who else by the way? **I** sat with damien and we together read the code and sent it.
When I stopped using Kernel-Extensions, and started using changesets to publish exactly the same code without method overrides, all of a sudden the same code became magically acceptable! You might be interested to know that more than 80-90% of what was Kernel-Extensions has already been added to pharo, so there wasnt so much wrong with it after all.
Not that much. I checked.
Its got nothing to do with replying or not.
Yes it is because I can ignore you completely too.
Its all to do with your team having the expertise to get SystemEditor working with Traits, for the good of all, but instead you spend time and effort forking MC, for the good of yourselves, and in the process trash a lot of time and effort expended for your benefit.
We are not doing that. We are running after time.
Its to do with your team forking SUnit unnecessarily etc etc
It is not my team, it is people with busy agenda not having the time to look at other packages
I consider the attitude conveyed by the words "No but we have the right to choose and consider if we like it or not." to be tantamount to snobbery, You saw how we worked with the settings and preference discussion with alain.
So Alain is external to your team? He had the courtesy of discussing the preferences ideas with the wider community, and for that I thanked him, and added him to my "non-rude" list.
Good!
Hang on... this is a list of projects, most of which dont have any code yet, and you are talking about rejecting stuff that doesnt meet your standards! That's exactly what I mean.
No I just warn you so that you do not get frustrated again.
If you spec out a project, plan it, and "contribute" to the team that works on it, then it will meet your standards by definition. Therefore there is no need to prejudice anything with such comments as "if 'their' work its not up to 'our' standards".
Exact! Keith hold on a moment. you are spining on yourself. We have a lot of deadlines, a lot of administration, I do pharo on my free time often the evening, I have no time to code what I want for my research, I fight all the time to get money, I have a huge pile of unfinished todos. So we all have more or less the same. So my contributions to something will be nearly null. Do you think that lukas can do more than seaside pier, phd, paper and books? Do you think that alex can do more than a start up, writing paper, fixing our code base on moose?
That's my whole point, you get the standards you want by participating in the process, not by looking down your nose at the contributions being hacked by some poor old stressed out full time carer.
But with the time constraints I have give feedback is the only thing I can do right now. Else I would have wrote another rio and lot more.
I am seriously considering licencing Rio under something other than MIT, so that you cant use it, until you change your attitude towards your potential benefactors.
Do it if you need, we will just not use it. Note that some people do not like rio design, so the fact that it is MIT does not mean that
These "some people", are more folks who have never sent me a single email discussing the design. And by the way Rio has had three complete redesigns since it was first written, incorporating various feedback and ideas.
Thankfully I have "some emails" from "some people" who like it
I imagine that too.
Keith
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project