3 ms·
Docker network effect is too important to ignore. That would be like swimming against the current. For example, Deno (https://deno.land/ https://deno.land/) in
by hu3 3y ago
Docker network effect is too important to ignore. That would be like swimming against the current.
For example, Deno (https://deno.land/ https://deno.land/) initially launched with precarious compatiliblity with Node.js, but eventually had to make compromises and adapt so Node.js projects could migrate easier.
- imiric 3y agoAll of that can be accomplished by being compatible with the broader OCI ecosystem. But Red Hat explicitly tries to be a Docker replacement (they suggest `alias docker=podman`, which actually breaks in many ways), to the point where I'm not sure why I should bother using a product that will always play catch-up to the real thing. This Desktop and Compose announcement is part of that roadmap, and I'm just wondering what Podman does better than Docker at this point.
- LeFantome 3y agoDo you do embedded? Look at the size of crun vs runc and at the portability of Go vs C. Do you like having to have a daemon running? I don’t. Also, the “pod” in the name may yield a few hints. Finally, despite all the recent and undeserved hate, I know that Red Hat will keep their source open. I have no such faith in Docker. Have you priced out Docker Desktop and Podman Desktop lately?
- freedomben 3y agoI find the Pod and Deployment support in Podman to be a killer feature personally. I've also gotten small apps running manually in podman, and once the config is working, podman can emit k8s compatible yaml that can be re-applied to a different podman or applied to a k8s cluster. Pretty sweet IMHO.
- imiric 3y agoThat's a good point, thanks. I haven't yet experimented with that.
- ragnese 3y ago> For example, Deno (https://deno.land/ https://deno.land/) initially launched with precarious compatiliblity with Node.js, but eventually had to make compromises and adapt so Node.js projects could migrate easier. And we have yet to see if that ends up being the right call. These things are always really tough. On the one hand, compatibility with existing stuff makes migration easier, but then if it's not actually different enough, we have no reason to change to the new thing.