That’s one thing - installing and trying out Podman compose takes less time than remembering where to get Docker compose from.
I always at least try it first, because it’s not expensive to try.
That’s one thing - installing and trying out Podman compose takes less time than remembering where to get Docker compose from.
I always at least try it first, because it’s not expensive to try.
Haha. Yes. This meme would be more fair to call “podman compose” out as “we have Docker compose at home”.
I’m not a fan of the compose pattern anyway. So it doesn’t usually bother me.
Interesting.
I used to do it the way you’re recommending (before I had podman compose), but I got tired of installing docker compose, and haven’t suffered enough for just using Podman compose, lately.
I do think more things are more likely to work the way you’re saying. Compose doesn’t seem to be standardized yet? And the original dev was probably using Docker compose - for any randomly selected project.
But when I can get away with podman compose, I do, as I recall it being much easier to setup.
Podman is the RedHat implementation of the Open Container Initiative (OCI).
A Dockerfile and a Containerfile are both OCI. Docker and Podman can generally both use either.
Contrasted with Docker, Podman has better security defaults, and installers and licenses that are both actually open source. (Parts of Docker are open source. Parts are not.)
Docker used to lead with additional features beyond OCI such as Docker Compose, but Podman Compose has been a thing for a while, now.
The more mature a product is, the more likely it works perfectly with any OCI compliant tool.
For rookie work, I feel like there’s still fair odds the developer only uses Docker and may rely on some anti-pattern that requires setting “bad security=ok” settings before their project will work in Podman.
Your mileage may vary.
I’ve had the opposite experience. Good to share our data points, though.
Docker desktop is not. (open source)
Which can be a pretty big deal.
This works out to: The product is unencumbered, but the only reliable installer is encumbered as fuck.
That’s a “no thanks”, from me.
I don’t need the sword of “Docker fucking with my colleague’s ability to collaborate” hanging over each of my projects.
I’m not mad at folks using Docker for backwards compatibility. I just don’t need to make the problem worse.


That guy is clearly an expert.
Not our fault everyone blows past the kind offer of : vimtutor on startup! (I kid. The default editor shouldn’t require a class.)
You’re 100% correct. Nano is a perfectly reasonable default.
That said, it is 2026. It also wouldn’t kill us to default to an interactive one-time prompt that defaults to nano, but offers one or two others, and removes itself after setting the user’s choice.
Like it cannot print invisible characters.
I was looking at an option to display invisible characters in Kate like last week. So it got better, I guess.
haha!
Sometimes I feel like my side of the holy war isn’t engaging in completely good faith.
I might switch sides to emacs if my fingers were long enough to reach the key combinations.
Maybe I’ll go try it, anyway!
…
What was the command to exit vi, again…?
But but but…vimtutor is right there on startup - so it’s an easily obtained diploma…
I’ll see myself out.
kate is fantastic, all around.
Ctrl+Alt+V makes the key bindings tolerable. (Vi mode)
Yes. Lack of :r! is what keeps me from using most editors that aren’t vim.
There’s so many things I don’t remember well enough to type accurately from memory, but I know the command to fetch quickly.


Human readable test code.


I felt that too!
I was a bit nervous, but mostly relieved not to worry that every boot into Windows could cost me my whole setup.
Now I’m going through a trying-not-to-preach phase. I just want my friends to feel as free of Microsoft’s bullshit as I do.


Yes. It’s pretty funny reading someone so confident in all the extra security they’re getting from Windows messing with their boot sequence, earlier in this thread.
Corporate OS is going to corporate. End users and private files are rarely winners when corporate needs to corporate hard.


I’ve had the same dual boot configuration since around 2018 and this never happens to me, yet I keep reading that it happens to others. I really wonder what I did differently.
We have very long memories.
In my defense, an OS that I paid for breaking my boot settings was such a virus thing to do, it was really memorable.


Fixed it by blowing away the Windows partition.
That’s how my dual booting experiment ended, as well.
Oh, thanks! I might try WSL next time, should I be so unfortunate, again.