Massive libxo-zation that breaks everything
bright at mu.org
Tue Mar 3 18:40:05 UTC 2015
Sent from my iPhone
> On Mar 3, 2015, at 9:32 AM, hiren panchasara <hiren at strugglingcoder.info> wrote:
>> On 03/02/15 at 07:33P, Alfred Perlstein wrote:
>> Actually I want to shame third party ports into adopting libxo (or at least providing machine readable output).
>> I know it's scary to try to lead the pack, after all we could be wrong, but maybe it's time to try something new and see what happens.
>> And no, your idea doesn't make sense it just will lead to those files bit rotting.
>> Bedsides that you don't even have a real spec other than "it should be done differently".
>> Again, show the code.
> Wow. He told you want he didn't like and he moved on. I hope/wish we as
> a project can take criticism more positively than this.
> Answer to every criticism should not be "show me your code". We (should)
> know better than that.
Maybe I am too old school but the motd on freefall is still "now shut up and code". I still believe that's right.
We ALL need to know when to step back from an issue we really do not have the bandwidth to constructively contribute to.
This doesn't mean ideas or concerns aren't valid, but that unless you truly have the bandwidth to contribute, taking a step back is a good idea.
More information about the freebsd-current