On Mon, Jul 3, 2017 at 10:19 AM, Bill Kontos vkontogpls@gmail.com wrote:
Also I don't consider going from a variety of options each with it's disadvantages to a single option essentially standardizing it a bad thing. It's just a lost opportunity to make a real standard for sure, but I don't think that's monoculture.
it's the very definition of a monoculture, bill.
a standard has multiple implementations: full documentation, stable APIs, a reference design plus alternative implementations (and/or people willing *to* implement alternative implementations).
where is the standard fully documented?
where is the definition of the stable APIs which have been set as "gold" and not subject to change for the next 10-20 years?
where is the reference design (with associated proper documentation)?
where are the alternative implementations?
l.