I would be worried about where that compose file is being stored. I keep my compose files in a git repo and after I edit them just do `docker compose up -d` (in fact, I hit a key in my editor and it runs that for me, showing the output).
Those are 2 hops as opposed to editing and applying the changes from a single interface. With git, assuming you are talking about an online repo, there is always the worry of accidentally leaking credentials etc. Though I assume the project mentioned here is all local so the compose files will be saved in a local directory.
I suppose the two methods (CLI and GUI) don't make much difference but they appeal to different users, maybe even different occasions for the power user.
