[Arm-netbook] severe systemd bugs (two of them)

[Troy Benjegerdes]

On Mon, Jul 03, 2017 at 12:05:59PM +0100, Luke Kenneth Casson Leighton wrote:
> On Mon, Jul 3, 2017 at 10:19 AM, Bill Kontos <vkontogpls at 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?

Gee, it's as if you're talking about bitcoin-core....

Developing all this stuff you speak of takes resources and
time to develop, test, deploy, support, maintain.

Do you have time to do it, or, at some point, do you have to
take work that pays? So if you want to monoculture problem,
then start figuring out how to build a **business model**
based on a diverse ecosystem.

My first suggestion would be start accepting something like
http://grantcoin.org as payment for your work, and for hardware,
for at least if that works, we might have developers that can
sign up for a basic income guarantee and work on whatever they
feel like working on, rather than code that will get them paid.

Or sell me a piece of libre-hardware that's pre-installed
**and QA tested** with a stack of libre-software that includes
all the designs so I can go down to my local silicon fab and
PCB house and have them make a derivative work.