install tldr and then you have easier commands

> tldr dd

  dd

  Convert and copy a file.
  See also: `caligula`.
  More information: https://www.gnu.org/software/coreutils/manual/html_node/dd-invocation.html.

  - Make a bootable USB drive from an isohybrid file (such as archlinux-xxx.iso) and show the progress:
    sudo dd if=path/to/file.iso of=/dev/usb_drive status=progress

  - Clone a drive to another drive with 4 MiB block size and flush writes before the command terminates:
    sudo dd bs=4M conv=fsync if=/dev/source_drive of=/dev/dest_drive

  - Generate a file with a specific number of random bytes by using kernel random driver:
    dd bs=100 count=1 if=/dev/urandom of=path/to/random_file

  - Benchmark the write performance of a disk:
    dd bs=1M count=1024 if=/dev/zero of=path/to/file_1GB

  - Create a system backup, save it into an IMG file (can be restored later by swapping if and of), and show the progress:
    sudo dd if=/dev/drive_device of=path/to/file.img status=progress

  - Check the progress of an ongoing dd operation (run this command from another shell):
    progress

Try:

man dd

A lot of devs don’t put much work into planning the flow of their GUI from a user’s perspective and it really shows.

IMHO a UI should offer everything a user can do in a given moment, readily available, nothing hidden behind more than a single menu. If something isn’t currently possible, it shouldn’t be available, and if the dev chooses to make the option visible but unavailable, it should be clearly and visibly marked as something that can be available (grayed out text for example).

I think devs tend to overestimate both the skill of the user, and the usefulness of their UI.

That’s when you go to alternativeto.net and get a different one. If you’re running into that problem then you just are using the wrong tools.

We’re talking about programs that are equally useful in both GUI and CLI, we’re not talking about libre office which is necessarily complex or a video editing program with a thousand transitions. Those are always going to be cryptic and always going to be GUI.

The problem with CLI is it can’t be made easier with a different interface.

I just had a stroke reading this.

bemselves and bings.

Look, you can’t bring thorn back like this. You only annoy your readers.

In the long run it more often than not is better to show them how to help themselves though. Let’s say they use Mint and want to install something they saw from ElementaryOS, so a new Flatpak repo: Of course in this moment I’d be done faster with their request for help sending them two commands to just paste, but showing them where they can add the new repo themselves and how this will make all the new apps pop up in their Software Store doesn’t just make them more independent and reassure them in trying things themselves, but will make it less likely for them to constantly ask you for help again.

And it makes more people stick with Linux, that’s always good.

CLI requires remembering commands though, or developing patience with your up arrow key.

And if you want help, is it “/h” or “/?” or “-h” or “—help” or “—h” or just “help”

I can’t remember that I need to pee, let alone what commands do what, save for my up arrow.

Don’t get me wrong, I’m in the terminal constantly, but I’ll pick a GUI over CLI every time if it’s an option.

That’s just wrong, the correct commands are always different. E.g. for journalctl to keep following the newest entries you need -f, while in dmesg you need -w for the very same feature. That’s not any more “the same” than it is the “same” to move your mouse around a differently organized GUI.

Writing in the CLI is comparable with moving the mouse, and remembering the appropriate commands of the specific tool comparable to know where to click on. However a proper GUI is immediately visible to be interacted with (and not abstract like most CLI arguments) and will convey function through form, while the function in the CLI is hidden behind help texts and man pages.

I do like working with the CLI a lot, but what you said was simply wrong.

Or pipe GUI output into another GUI function.

Or >> log.txt

So you want newbies blindly entering scripts to there command line and not knowing what that are doing.

Yep, this is just one factor. It’s difficult for people not to judge a book by its cover.

Correctly done, cli is superior for a lot of things.

basic_task_list = ['copy and paste', 'install package', 'type', 'keyboard', 'read and write' ]

for basic_task in basic_task_list:
    print(f"""
        Newbies can't {basic_task}.
        They never {basic_task} in windows.
        Windows  has replaced {basic_task} with copilot, this is what linux needs to do to compete.

        How will linux ever hope to attract windows user if it still maintains this ancient hacker 1337xor tools like  {basic_task}?

        Users just want to turn on computer and watch it do computance - how does linux not get this?
    """)

“Join our Discord server!”

deleted by creator

ffmpeg ❌

ffmpreg ✔️

Interesting. Their website would make me run away fearing it’s from a cheap fake download button scam from ten years ago, but the software itself looks pretty legit.