Date: Tue, 3 Mar 2015 12:02:19 -0800 From: Justin Hibbits <jrh29@alumni.cwru.edu> To: Alfred Perlstein <bright@mu.org> 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: <CAHSQbTDCA0AkOmsD55SuDYXiaZ7i8-%2BzKkK4ZPoA46gvi41W5g@mail.gmail.com> In-Reply-To: <569FDEF4-D6D1-4994-A30B-9D9BCE8B1858@mu.org> 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> <569FDEF4-D6D1-4994-A30B-9D9BCE8B1858@mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 3, 2015 at 11:14 AM, Alfred Perlstein <bright@mu.org> wrote: > > >> 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? > > -Alfred libifying base. And, if there's still stuff that needs libxo'd, do that, too. Looking at both could help to derive a clean library API that libxo'd interfaces can use. libifying base has been on my "interesting TODO" list for the last 10 years or so, I just haven't had the inclination. Now that there's been a swell of support for it, getting people together to actually make it happen seems like a good idea. - Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHSQbTDCA0AkOmsD55SuDYXiaZ7i8-%2BzKkK4ZPoA46gvi41W5g>