←back to thread

917 points cryptophreak | 1 comments | | HN request time: 0.335s | source
Show context
andreldm ◴[] No.45761642[source]
If handbrake scares them, don’t you dare to demonstrate how to use ffmpeg. I remember when I used handbrake for the first time and thought “wow, it’s much more convenient than struggling with ffmpeg”.
replies(7): >>45761715 #>>45761913 #>>45761996 #>>45762179 #>>45762626 #>>45762929 #>>45764672 #
soraminazuki ◴[] No.45762626[source]
If you only care about converting media without tweaking anything, ffmpeg offers the simplest UI ever.

    ffmpeg -i input.avi output.mp4
replies(3): >>45762850 #>>45766399 #>>45769237 #
a_shovel ◴[] No.45762850[source]
Proposing a CLI command as a candidate for "simplest UI ever" is a great gag.
replies(1): >>45763048 #
ekjhgkejhgk ◴[] No.45763048[source]
Come on. "type ffmpeg, then hyphen i then the input filename then the output filename". I would've understood this when I was 8. Because I was super smart? No, because I was making a genuine effort.
replies(5): >>45763358 #>>45764401 #>>45765442 #>>45767638 #>>45770301 #
pwg ◴[] No.45763358[source]
The portion you've overlooked is there is an entire population of users out there who have never seen, nor used, a command line, and telling them to "just type this out" ignores all the background command line knowledge necessary to successfully "just type this out":

1) They have to know how to get to a command line somewhere/how (most of this group of users would be stymied right here and get no further along);

2) They now have to change the current directory of their CLI that they did get open to the location in their filesystem where the video is actually stored (for the tiny sliver who get past #1 above, this will stymie most of them, as they have no idea exactly where on disk their "Downloads" [or other meta-directory item] is actually located);

3) For the very few who actually get to this step, unless they already have ffmpeg installed on their PATH, they will get a command not found error after typing the command, ending their progress unless they now go and install ffmpeg;

4) For the very very few who would make it here, almost all of them will now have to accurately type out every character in "a-really_big_filename with spaces .mov", as they will not know anything about filename completion to let the shell do this for them. And if the filename does have spaces, and many will, they now need to somehow know 4a) that they have to escape the spaces and 4b) how to go about escaping the spaces, or they will instead get some ffmpeg error (hopefully just 'file not found', but with the extra parameters that unescaped spaces will create, it might just be a variant of "unknown option switch" error instead).

replies(6): >>45763837 #>>45764041 #>>45764529 #>>45764921 #>>45765189 #>>45766623 #
1. soraminazuki ◴[] No.45765189[source]
The reality is that we've been infantilizing users for far too long. The belief that people can't handle fundamental concepts is misguided and primarily serves to benefit abusive tech companies.

Two decades ago, users understood what "C:\Documents and Settings\username\My Documents" meant and navigated those paths easily. Yet, we decided they were too "stupid" to deal with files and file paths, hiding them away. This conveniently locked users into proprietary platforms. Your point #2 reflects a lie we've collectively accepted as reality. Sadly, too many people now can’t even imagine that a straightforward way to exchange data among different software once existed, but that's a situation we're deliberately perpetuating.

This needs to change. Users deserve the opportunity to learn and engage with their tools rather than being treated as incapable. It’s time we started empowering users for a change.