3 ms·

I am so not understanding the purpose of this... If you need Docker CLI commands, isn't it just easier to use the CLI that you're already on? Docker is fully

by mmh0000 9mo ago

I am so not understanding the purpose of this... If you need Docker CLI commands, isn't it just easier to use the CLI that you're already on? Docker is fully self-documented: / # docker Usage: docker [OPTIONS] COMMAND A self-sufficient runtime for containers Common Commands: run Create and run a new container from an image exec Execute a command in a running container …SNIP… / # docker run --help Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] Create and run a new container from an image Aliases: docker container run, docker run Options: --add-host list Add a custom host-to-IP mapping (host:IP) …SNIP…

fragmede 9mo ago
Are you on a desert island with no access to the Internet? If you don't know docker, what's faster? Reading all of the documentation first and then figuring out the difference between, say, run and exec, or just copy and pasting a command from a tutorial until it sinks in and you gain a better understanding? This is the AI information age. If docker has eaten your hard drive, and again, you don't know docker, is it easier to have ChatGPT tell you, or muddle around with ps, rm, images, rmi and all of the various options. If you have a command with a bunch of flags, static documentation like man pages are just such a poor interface compared to eg explainshell.com. This opinion obviously gets me thrown out of the Unix grey beards club, but I don't have a beard and it's not grey.
- rendaw 9mo ago
  How do you know which command to copy and paste? Unless you're suggesting to just try them randomly until you get one that seems to do what you want. There are plenty of commands where the documentation is nearly impenetrable (e.g. ffmpeg, or if it exists at all), but I think GP's point was that for docker it's fairly simple. IMO except for the concrete examples for docker run/exec, this website looks more or less exactly like the CLI help output for docker.
- allarm 9mo ago
  > what's faster? What a terrible question. Why do you think speed is a good metric? Why is it better to copy-paste in 2 seconds than to read the manual for 20 minutes and learn the basics? What would have happened?
  - fragmede 9mo ago
    > Why do you think speed is a good metric? Because time is the great equalizer. Everyone only gets 86400 seconds in the day. How you spend them is up to you. There are some things with a very steep learning curve, like vim, that one decides for themselves if it's worth investing their time in to learn. Or not. Most things have a shallower learning curve though, thankfully. The first time you interact with Docker, how do you know you're ever going to use it again? How do you know you're going to reap rewards of those 20 minutes. How do you know which of the dozen random tool you come across on a stroll of the Internet is worth investing the 20 minutes? Apriori, you can't. So you copy and paste in 2 seconds, and if it turns out that you use that tool more than once, then go take those 20 minutes and learn how to use it right and use it well. What's the opportunity cost of those 28 minutes? What other piece of technology could this user have been learning? Is there something more appropriate for their particular role? Maybe it's something that's not even computer related that's important for their life.
    - allarm 9mo ago
      > Because time is the great equalizer. Everyone only gets 86400 seconds in the day. How you spend them is up to you. It is important to remember that while this is true time is not the ONLY criteria.
anagogistis 9mo ago
I’m not trying to replace docker --help or man pages. The goal is basically to package the same info in a nicer, modern UI that’s more pleasant to use than terminal help output. I’ll also add more things like "Recipes". This was just the first version. But you’re always free to use whatever you prefer.

by mmh0000 9mo ago

fragmede 9mo ago

Are you on a desert island with no access to the Internet? If you don't know docker, what's faster? Reading all of the documentation first and then figuring out the difference between, say, run and exec, or just copy and pasting a command from a tutorial until it sinks in and you gain a better understanding? This is the AI information age. If docker has eaten your hard drive, and again, you don't know docker, is it easier to have ChatGPT tell you, or muddle around with ps, rm, images, rmi and all of the various options. If you have a command with a bunch of flags, static documentation like man pages are just such a poor interface compared to eg explainshell.com. This opinion obviously gets me thrown out of the Unix grey beards club, but I don't have a beard and it's not grey.

rendaw 9mo ago
How do you know which command to copy and paste? Unless you're suggesting to just try them randomly until you get one that seems to do what you want. There are plenty of commands where the documentation is nearly impenetrable (e.g. ffmpeg, or if it exists at all), but I think GP's point was that for docker it's fairly simple. IMO except for the concrete examples for docker run/exec, this website looks more or less exactly like the CLI help output for docker.
allarm 9mo ago
> what's faster? What a terrible question. Why do you think speed is a good metric? Why is it better to copy-paste in 2 seconds than to read the manual for 20 minutes and learn the basics? What would have happened?
- fragmede 9mo ago
  > Why do you think speed is a good metric? Because time is the great equalizer. Everyone only gets 86400 seconds in the day. How you spend them is up to you. There are some things with a very steep learning curve, like vim, that one decides for themselves if it's worth investing their time in to learn. Or not. Most things have a shallower learning curve though, thankfully. The first time you interact with Docker, how do you know you're ever going to use it again? How do you know you're going to reap rewards of those 20 minutes. How do you know which of the dozen random tool you come across on a stroll of the Internet is worth investing the 20 minutes? Apriori, you can't. So you copy and paste in 2 seconds, and if it turns out that you use that tool more than once, then go take those 20 minutes and learn how to use it right and use it well. What's the opportunity cost of those 28 minutes? What other piece of technology could this user have been learning? Is there something more appropriate for their particular role? Maybe it's something that's not even computer related that's important for their life.
  - allarm 9mo ago
    > Because time is the great equalizer. Everyone only gets 86400 seconds in the day. How you spend them is up to you. It is important to remember that while this is true time is not the ONLY criteria.

anagogistis 9mo ago

I’m not trying to replace docker --help or man pages. The goal is basically to package the same info in a nicer, modern UI that’s more pleasant to use than terminal help output. I’ll also add more things like "Recipes". This was just the first version. But you’re always free to use whatever you prefer.