A new upstream project to break up Docker into independent components

Re:A new upstream project to break up Docker into independen... by user5994461 on Thursday April 20, 2017 @01:48PM (#14159021)

When you tell your boss you adopted moby, he's like "WTF is that?!".

If you were already migrating to Docker, now you have to explain that the project name changed overnight without explanation, and it's hurting your credibility pretty bad. It's also gonna bring a lot of confusion onto everyone for a very long time.

[ Parent | on HN ]

Re:A new upstream project to break up Docker into independen... by douche on Thursday April 20, 2017 @02:32PM (#14159444)

Or equally likely, "That electronic musician from the 90s? Huh?"

[ Parent | on HN ]

Re:A new upstream project to break up Docker into independen... by jfoutz on Friday April 21, 2017 @01:38AM (#14163330)

Use the tried and true engineer response. Docker does many things because it has to be all things to all people. Docker is composed entirely from Moby, we're only composing the parts that matter to our organization. It'll be faster, use less resources. Even better, it reduces our attack surface because we're removing all that stuff less experienced teams need to muddle through their deployments.

The three points seem to be, cheaper, more secure, and the other guys are dumb.

[ Parent | on HN ]