From owner-freebsd-current@freebsd.org  Sun Nov 15 17:37:57 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 211EDA30E38
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 15 Nov 2015 17:37:57 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com
 [IPv6:2607:f8b0:4001:c06::232])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id E2E3A134B
 for <freebsd-current@freebsd.org>; Sun, 15 Nov 2015 17:37:56 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: by iofh3 with SMTP id h3so140206193iof.3
 for <freebsd-current@freebsd.org>; Sun, 15 Nov 2015 09:37:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=MRCWGCYKTw5ljZiWQxhHWDQyUul+epFGXjAXk9Tm4nM=;
 b=AQF0RBbINrZlLBkXTZS7pHfFv0cvgquI61+cJa/CA3KKFtmDF6LfjRTweNWZ5rse+A
 jo8v3Hg0onjFdEjS27qbJtUuIb49ByaaAyX9qdk8oUfXdF7LNmOB/FN/Z3HhY7R2v9vi
 U9RGbu0EpgrRDjFLGSEnZDPDhDy21HPOn+o7acHB8CftDi9HgyzVQJ9UvkTSLy8q4jqD
 UvBQRlJI2HZ0vId5BIibM0VSO/HLHLeNJIkZJxNifZ2ta4+sxzrhRjD0Vq1Mw9RNPLDt
 Uld0vClcVOc4X0gNP+zyAIxtyeg5wem6MYiknIcselacBlraYxwrnzcks1VniQPEAWQX
 dOUQ==
MIME-Version: 1.0
X-Received: by 10.107.162.21 with SMTP id l21mr1380326ioe.123.1447609075974;
 Sun, 15 Nov 2015 09:37:55 -0800 (PST)
Received: by 10.36.217.196 with HTTP; Sun, 15 Nov 2015 09:37:55 -0800 (PST)
In-Reply-To: <702A1341-FB0C-41FA-AB95-F84858A7B3A4@rdsor.ro>
References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro>
 <CAJ-Vmokfo_BGWji9TrgQ40oRxqht9-2iEZVon7aQxR_93Ufxyg@mail.gmail.com>
 <702A1341-FB0C-41FA-AB95-F84858A7B3A4@rdsor.ro>
Date: Sun, 15 Nov 2015 09:37:55 -0800
Message-ID: <CAJ-VmoniBAmWTf9MkCCMYhRbPLc=0+z5kRSijXfqX9VZvm8jDg@mail.gmail.com>
Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues?
From: Adrian Chadd <adrian.chadd@gmail.com>
To: Dan Partelly <dan_partelly@rdsor.ro>
Cc: freebsd-current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Nov 2015 17:37:57 -0000

On 15 November 2015 at 09:10, Dan Partelly <dan_partelly@rdsor.ro> wrote:
> Meaning, is that simple to push things in head , if somone does the work, even with with no proper review of the problem at hand , and the proposed solutions ?

Nope and yup. The juniper folk had a solution to a problem multiple
people had requested work on, and their proposal was by far the
furthest along code and use wise.

It's all fine and good making technical decisions based on drawings
and handwaving and philosophizing, but at some point someone has to do
the code. Juniper's libxo was the furthest along in implementation and
production.


-a