That's literally like asking "What car has the best driving experience?". There is no one answer.
If you want something that "just works," Linux Mint[1] is a great starting point. That gets you into Linux without any headache. Then, later when bored, you can branch out into the thousands[2] of Linux distributions that fill every possible niche
I would never, recommend anything from Debian-family for consumer use. Its literally outdated linux, under the marketing 'stable'.
Fedora is so significantly better.
I wouldn't confuse popularity for good. Ubuntu gave away free CDs in the 2000s and are living off old marketing.
Debian family is so bad. You will be in the terminal constantly just trying to get stuff to work. Stick to a well maintained, up to date, consumer distro, Fedora.
But you've got to admit that OPs tool does it quicker, except if you like to memorize flags or already have a script specifically for this. And it's much nicer on the eye than most (all?) nmap-guis out of the box.
The goal has never been to create something that can replace nmap, the goal was to learn more about networking and about building TUIs in Go. Honestly I am quite overwhelmed by the amount of traction it got today, definitely not what I expected.
I am very grateful for all the feedback and suggestions, and I will take my time to evaluate every comment. In the coming weeks I will try to implement most of the feedback and do releases to improve the tool further, thanks everyone!
Bah. It's what chrome on Android is doing now when I ask it to give me the link. Fixed it. Thanks!
I had searched for it in the search bar at the bottom of the home screen, which opened it in a chrome window. If you tap the share icon on the top right, you get the share.google link. If you tap the three dots and then something like "copy link" you get the actual link.
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…
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.
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.
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?
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.
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.
In practice: https://en.wikipedia.org/wiki/In_re_Boucher
The government gets what the government wants.
reply