I’ll have to give it another try.

I should clarify that the issues I had were podman compose being able to run unaltered compose files that worked with docker compose, many of which were fairly complicated. It may have been adequate for simpler use cases back when I tried it.

In my experience podman compose is not a sufficient replacement.

Docker compose can be used with podman via the podman socket daemon. It’s very easy to get working. Give it a try.

Yep. I use both quite a bit. Chocolatey is great!

The point Im trying to make is package managers are better suited for developers and the lack of a great alternative for installing software on the distros I’ve used is not helping with the mass appeal of Linux.

I could be wrong here as I’ve never tried any of the “home computer” distros (mint, ubuntu).

Why do you think its bad? From a secruity standpoint its obviously not great, but its undeniably more convenient than running a curl command to pull in a third party .repo file, yum update and yum install to get something that isnt easily available in my base repos.

Im not sure the software center being half baked is even the real problem.

One of the nice things about Windows is that you dont need a central, curated, repository for software. You can google the thing you want and just download an msi/exe of the latest stable version and, 99.9% of the time, leading back to your first point, it will just work.

This is what prevented me from using podman, unfortunately. That and the setup for devcontainers in vscode wasnt exactly seamless.

Unfortunate since their windows support is great.

You need a space between your ‘#’ and text for markdown headings (unless you wanted to do it that way in which case ignore me). Great post!