From owner-freebsd-current@FreeBSD.ORG Tue Mar 3 18:40:05 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F5CC4DD; Tue, 3 Mar 2015 18:40:05 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 35E8B686; Tue, 3 Mar 2015 18:40:05 +0000 (UTC) Received: from [10.211.109.92] (unknown [216.205.235.226]) by elvis.mu.org (Postfix) with ESMTPSA id 01191341F87C; Tue, 3 Mar 2015 10:40:03 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Massive libxo-zation that breaks everything From: Alfred Perlstein X-Mailer: iPhone Mail (12B440) In-Reply-To: <20150303173223.GQ95752@strugglingcoder.info> Date: Tue, 3 Mar 2015 10:39:53 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <93307065-F026-42DE-A2D2-3843619BAD1A@mu.org> References: <54F34B6E.2040809@astrodoggroup.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> <20150303173223.GQ95752@strugglingcoder.info> To: hiren panchasara Cc: Harrison Grundy , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Mar 2015 18:40:05 -0000 Sent from my iPhone > On Mar 3, 2015, at 9:32 AM, hiren panchasara w= rote: >=20 >> On 03/02/15 at 07:33P, Alfred Perlstein wrote: >>=20 >>>>=20 >>=20 >> Actually I want to shame third party ports into adopting libxo (or at lea= st providing machine readable output).=20 >>=20 >> I know it's scary to try to lead the pack, after all we could be wrong, b= ut maybe it's time to try something new and see what happens.=20 >>=20 >> And no, your idea doesn't make sense it just will lead to those files bit= rotting. =20 >>=20 >> Bedsides that you don't even have a real spec other than "it should be do= ne differently".=20 >>=20 >> Again, show the code. >=20 > 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. >=20 > 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. =20 We ALL need to know when to step back from an issue we really do not have th= e bandwidth to constructively contribute to.=20 This doesn't mean ideas or concerns aren't valid, but that unless you truly h= ave the bandwidth to contribute, taking a step back is a good idea.=20 -Alfred.=20