Re: libXO-ification - Why - and is it a symptom of deeper issues?

On 15 November 2015 at 09:10, Dan Partelly <dan_partelly_at_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