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.

Oops. Thanks for the correction.

I hadn’t heard of quadlets. I’ll have to give them a look.

We’ve completely transitioned from docker to podman where I work. The only pain point was podman compose being immature compared to docker compose, but turns out you can run docker compose with podman using the podman socket easily.

Agree. I may be misunderstanding something here, but to view votes one would have to spin up their own instance. This would prevent your average abusive moron from harassing users who down voted their post/comment.

Reminds me of this

Typically, I can read an “average” open source programmers code. One of the issues I have with C++ is the standard library source seems to be completely incomprehensible.

I recently started learning rust, and the idea of being able to look at the standard library source to understand something without having to travel through 10 layers of abstraction was incredible to me.

Agree with this. I think tactfully pointing out minor issues you see can be helpful because the implementor is closer to the problem and may have just overlooked the issue and can come up with a solution easily. I’ve been on the giving and receiving end of this, and so long as everyone is behaving professionally, it’s always been helpful.

On the “tactful” note, I’ll generally say something like: “I don’t have a solution, but I see problem. I don’t know that this is reason enough to hold up this PR. I’ll leave it up to you.”

I am but I’m very quickly finding out I have nothing to contribute.