undefined | Better HN

0 pointscoldtea11y ago0 comments

>it appears no Docker employee has ever contributed a single line of code to the LXC implementation itself (that would be hard work, rather than bikeshedding userspace tools, after all)

You keep using this word, bikeshedding. I don't think it means what you think it means.

http://en.wiktionary.org/wiki/bikeshedding

http://www.urbandictionary.com/define.php?term=bikeshedding

TL;DR; it's about discussing/debating trivial details instead of the important characteristics of a system, not about working on easy stuff vs more hard programs.

0 comments

2 comments · 1 top-level

kordless11y ago· 1 in thread

> while neglecting the design of the power plant itself

I think what hosay123 is trying to say is that LXC is the power plant and the tooling around it is Docker, which runs in userspace. Note I'm not trying to say that, I'm just saying things.

coldteaOP11y ago

That's what I got from his comment too.

But the first difference (with bikeshedding) is that bikeshedding is not "doing the tooling around the power plant instead of the plant itself" but spending time discussing and designing some insignificant detail instead of the power plant.

(That is: bikeshedding is getting lost in DEBATING the easy and incosequential details of an implemntation).

Docker is neither "lost in discussion" (they're building things, and a lot, and fast), nor a trivial detail (that would be e.g. LXC code's tabs vs spaces convention etc).

j / k navigate · click thread line to collapse