Date: Tue, 3 Mar 2015 11:14:19 -0800 From: Alfred Perlstein <bright@mu.org> To: Justin Hibbits <jrh29@alumni.cwru.edu> Cc: Harrison Grundy <harrison.grundy@astrodoggroup.com>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, hiren panchasara <hiren@strugglingcoder.info> Subject: Re: Massive libxo-zation that breaks everything Message-ID: <569FDEF4-D6D1-4994-A30B-9D9BCE8B1858@mu.org> In-Reply-To: <CAHSQbTD9%2BgaxA-28FuHz4-UP4mBSKzcRg9CB4DQ1yGLA0DAd_Q@mail.gmail.com> References: <54F34B6E.2040809@astrodoggroup.com> <CAG=rPVfcB1Fy_8mHq-t5Ay07yrzuSGthQ0ZcGzvp0XG9gSSzkg@mail.gmail.com> <54F35F29.4000603@astrodoggroup.com> <54F429EF.5050400@freebsd.org> <54F46536.8040607@mu.org> <54F4C03F.7030704@freebsd.org> <54F4FECB.90501@freebsd.org> <197AA5DC-0591-4F71-BF10-51A5D8104C11@mu.org> <54F5270D.1010009@freebsd.org> <E187B006-72D8-40CB-A5F0-439B1D02E037@mu.org> <20150303173223.GQ95752@strugglingcoder.info> <93307065-F026-42DE-A2D2-3843619BAD1A@mu.org> <CAHSQbTD9%2BgaxA-28FuHz4-UP4mBSKzcRg9CB4DQ1yGLA0DAd_Q@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> On Mar 3, 2015, at 11:07 AM, Justin Hibbits <jrh29@alumni.cwru.edu> wrote: > >> On Tue, Mar 3, 2015 at 10:39 AM, Alfred Perlstein <bright@mu.org> wrote: >> >> >> Sent from my iPhone >> >>>> On Mar 3, 2015, at 9:32 AM, hiren panchasara <hiren@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. >> >> -Alfred. > > You're both right. Maybe we need a hackathon on this. Is BSDCan too late? Hackathon on what exactly? -Alfredhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?569FDEF4-D6D1-4994-A30B-9D9BCE8B1858>