Re:CoreOS is building a container runtime, Rocket
by frostmatthew on Monday December 01, 2014 @06:29PM
(#8684751)
> You are not "locked in" by Docker Inc if you are using Docker just like you aren't locked in by Github if you are using git.
A much more accurate analogy would be you are not "locked in" by Oracle if you are using MySQL. It may be true today, but no guarantee that will always be the case.
Re:CoreOS is building a container runtime, Rocket
by mikerichards on Monday December 01, 2014 @10:56PM
(#8685630)
Despite the attempt of some to move goal posts, you're still guaranteed that you won't be locked in by Oracle even tomorrow. You still have the source code for the version you're running right?
Re:CoreOS is building a container runtime, Rocket
by jmnicolas on Wednesday December 03, 2014 @05:20AM
(#8692876)
" You still have the source code for the version you're running right?"
Yes but I don't have the skill, time, resources and will to maintain MySQL if and when Oracle goes evil (I mean more evil than now ;-)
This is why I choose carefully what companies / groups I depend on for my future computing needs.
Re:CoreOS is building a container runtime, Rocket
by frostmatthew on Monday December 01, 2014 @11:39PM
(#8685749)
Sure...as long as I don't care about security patches, bug fixes, performance improvements, or new features.
Re:CoreOS is building a container runtime, Rocket
by hobofan on Tuesday December 02, 2014 @04:37AM
(#8686365)
If people think the software moves in the wrong direction it will be forked (see MariaDB). Nothing world changing will happen.
Docker Inc. seems to make a lot of effort to ensure Docker is a truely open project. I get the feeling that people think that handing your project to Apache is the only way to prevent vendor lock in these days.
You are not "locked in" by Docker Inc if you are using Docker just like you aren't locked in by Github if you are using git.