Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Jun 2015 09:47:09 -0600
From:      Ian Lepore <ian@freebsd.org>
To:        David Chisnall <theraven@FreeBSD.org>
Cc:        Steve Kargl <sgk@troutmask.apl.washington.edu>, Alexander Kabaev <kabaev@gmail.com>, Marcel Moolenaar <marcel@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r284198 - head/bin/ls
Message-ID:  <1434210429.1415.65.camel@freebsd.org>
In-Reply-To: <C88CB169-12FE-4692-92AA-5C7D41BB61DF@FreeBSD.org>
References:  <201506100127.t5A1RdX6051959@svn.freebsd.org> <20150612204309.11dd3391@kan> <20150613024916.GA98218@troutmask.apl.washington.edu> <1434208622.1415.57.camel@freebsd.org> <C88CB169-12FE-4692-92AA-5C7D41BB61DF@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2015-06-13 at 11:38 -0400, David Chisnall wrote:
> On 13 Jun 2015, at 11:17, Ian Lepore <ian@freebsd.org> wrote:
> > 
> > If you would have told me a year ago that you had a simple scheme that
> > could make 30 years of experience maintaining code for unix-like systems
> > completely worthless I would have been skeptical, but it seems we're
> > well on our way.
> 
> There is a lot of heckling and unhelpful hyperbole in this thread.  Reading the xo_emit format strings takes a little bit of getting used to, but the same is true of printf - it˘s just that we˘re already used to printf.  The structured parts (xo_open_container, xo_close_container and friends) are clear and descriptive.  The changes are fairly invasive, but the benefits are also very large for anyone who is wanting to automate administration of FreeBSD systems.
> 
> If you have suggestions for how the libxo APIs could be improved, then please let us know - Phil is very reception to suggestions but objections along the lines of Ħit˘s not what I˘m used to and changes sometimes break things so we should never have changes˘ are not helpful.
> 

"This is a piece of crap that needs to be excised from the system and
done a different way" is useful input whether you agree with it or not.
The idea that someone does not have the right to point out a huge
mistake simply because they don't have a patchset in hand is pure BS.

But, this is what you get when a disagreement about design is "solved"
by someone pointing out that project policy has always been "he who
commits first wins the design discussion" and that's pretty much what
happened when all of this was being discussed.

-- Ian





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1434210429.1415.65.camel>