Docker does not lock you in with the docker hub though. So no hostage taking.
While that isn't false, defaults carry immense weight. Also, very few have the means to host at scale like Docker Hub; if the goal is to not just repeat the same mistake later, each project would have to host their own, or perhaps band together into smaller groups. And unfortunately, being a good programmer does not make you good at devops or sysadmin work, so now we need to involve more people with those skillsets.
To be clear, I'm totally in favor of this kind of fragmentation. I'm just also realistic about what it means.
Linuxserver.io images don't come directly from Docker Hub any more, and I don't know if anyone noticed or cared. They use their own domain lscr.io that redirects to the Docker repository they're using (currently Github) which makes it easy for them to move the repository without breaking things for users. https://www.linuxserver.io/blog/wrap-up-warm-for-the-winter
That approach is a good idea in general. If you're running a medium to large size project, never directly rely on domain names you don't control because it makes it painful to migrate to something else in the future. Even if your own domain just has a bunch of redirects (both URL redirects and email forwarding), it's better than nothing.
That's the same as saying that Microsoft doesn't make anyone hostage with MS Office, yet they do.
Bullshit. I can use docker without the docker hub very easily. Anyone can host docker images, and docker allows this, no weird hacks needed.
They don't though? The file formats are documented and other office suite software can read and write them.
They do, those formats are a mess, full of small details and non-standard implementations on MS Office and Excel is most like the worst case. Office formats are all open until you realize that means shit because Microsoft does what they want and the standards don't cover everything. If you're serious about office and you need to collaborate with MS Office users those "other office suites" won't cut it. You'll have compatibility issues.
I agree that they're a mess, but there's nothing in there that intentionally holds you hostage. The format is not binary - it's readable to anyone that wants to read it.
Docker does not lock you in with the docker hub though. So no hostage taking.
While that isn't false, defaults carry immense weight. Also, very few have the means to host at scale like Docker Hub; if the goal is to not just repeat the same mistake later, each project would have to host their own, or perhaps band together into smaller groups. And unfortunately, being a good programmer does not make you good at devops or sysadmin work, so now we need to involve more people with those skillsets.
To be clear, I'm totally in favor of this kind of fragmentation. I'm just also realistic about what it means.
Linuxserver.io images don't come directly from Docker Hub any more, and I don't know if anyone noticed or cared. They use their own domain lscr.io that redirects to the Docker repository they're using (currently Github) which makes it easy for them to move the repository without breaking things for users. https://www.linuxserver.io/blog/wrap-up-warm-for-the-winter
That approach is a good idea in general. If you're running a medium to large size project, never directly rely on domain names you don't control because it makes it painful to migrate to something else in the future. Even if your own domain just has a bunch of redirects (both URL redirects and email forwarding), it's better than nothing.
That's the same as saying that Microsoft doesn't make anyone hostage with MS Office, yet they do.
Bullshit. I can use docker without the docker hub very easily. Anyone can host docker images, and docker allows this, no weird hacks needed.
They don't though? The file formats are documented and other office suite software can read and write them.
They do, those formats are a mess, full of small details and non-standard implementations on MS Office and Excel is most like the worst case. Office formats are all open until you realize that means shit because Microsoft does what they want and the standards don't cover everything. If you're serious about office and you need to collaborate with MS Office users those "other office suites" won't cut it. You'll have compatibility issues.
I agree that they're a mess, but there's nothing in there that intentionally holds you hostage. The format is not binary - it's readable to anyone that wants to read it.
Do you have an example?