I’ve got to say, some Linux people’s fetish for running everything from the command line gets just creepy at times.
-
I’ve got to say, some Linux people’s fetish for running everything from the command line gets just creepy at times.
I mean things like “why click a button when you could memorize yet another command instead?” pushed to extremes. I don’t want to memorize a text command to play or pause my music, dude.
“Why click a couple of buttons in a GUI when you can instead slowly drive yourself mad trying futilely to remember the proper syntax for a ffmpeg command?”
EDIT: I love providing TWO examples of the command line being an accessibility nightmare, only for people to argue that ackshually, the real accessibility nightmare is not having to type “
ffmpeg -ss 01:28:05.035 -to 01:28:14.461 -copyts -i "input.mp4" -ss 01:28:05.035 -to 01:28:14.461 -c:v libx264 -crf 17 -b:v 1M -vf "subtitles=subtitle.srt,scale=-1:320,format=yuv420p" -c:a aac -af "pan=stereo|FL=0.5*FC+0.707*FL+0.707*BL+0.5*LFE|FR=0.5*FC+0.707*FR+0.707*BR+0.5*LFE" -movflags +faststart output.mp4” entirely from memory. -
I’ve got to say, some Linux people’s fetish for running everything from the command line gets just creepy at times.
I mean things like “why click a button when you could memorize yet another command instead?” pushed to extremes. I don’t want to memorize a text command to play or pause my music, dude.
“Why click a couple of buttons in a GUI when you can instead slowly drive yourself mad trying futilely to remember the proper syntax for a ffmpeg command?”
EDIT: I love providing TWO examples of the command line being an accessibility nightmare, only for people to argue that ackshually, the real accessibility nightmare is not having to type “
ffmpeg -ss 01:28:05.035 -to 01:28:14.461 -copyts -i "input.mp4" -ss 01:28:05.035 -to 01:28:14.461 -c:v libx264 -crf 17 -b:v 1M -vf "subtitles=subtitle.srt,scale=-1:320,format=yuv420p" -c:a aac -af "pan=stereo|FL=0.5*FC+0.707*FL+0.707*BL+0.5*LFE|FR=0.5*FC+0.707*FR+0.707*BR+0.5*LFE" -movflags +faststart output.mp4” entirely from memory.@erkhyan because the command line doesn't rely on some flutter or react framework with dubious accessibility because of some dev reusing and kludging a component from somewhere else or forgetting to label the button. The learning curve for the CLI is steeper, but when I hit enter it will work. A command is difficult. An inaccessible button means I have to find new software
-
@erkhyan because the command line doesn't rely on some flutter or react framework with dubious accessibility because of some dev reusing and kludging a component from somewhere else or forgetting to label the button. The learning curve for the CLI is steeper, but when I hit enter it will work. A command is difficult. An inaccessible button means I have to find new software
@PepperTheVixen The accessibility argument in my case runs directly into the face of “I can and will forget a text command but can never forget what a GUI element looks like”
-
@PepperTheVixen The accessibility argument in my case runs directly into the face of “I can and will forget a text command but can never forget what a GUI element looks like”
@erkhyan @PepperTheVixen Accessibility looks like different things to different people.
To someone with difficulty walking and standing, driving a car is more accessible than taking the bus. But to a blind person, the bus is more accessible than driving.
Pepper is blind and GUIs can be quite inconsistent in their compatibility with screen readers and other tools used by blind computer users. Meanwhile for the averagely abled user the GUI is easier to use most of the time. -
R relay@relay.mycrowd.ca shared this topic
-
I’ve got to say, some Linux people’s fetish for running everything from the command line gets just creepy at times.
I mean things like “why click a button when you could memorize yet another command instead?” pushed to extremes. I don’t want to memorize a text command to play or pause my music, dude.
“Why click a couple of buttons in a GUI when you can instead slowly drive yourself mad trying futilely to remember the proper syntax for a ffmpeg command?”
EDIT: I love providing TWO examples of the command line being an accessibility nightmare, only for people to argue that ackshually, the real accessibility nightmare is not having to type “
ffmpeg -ss 01:28:05.035 -to 01:28:14.461 -copyts -i "input.mp4" -ss 01:28:05.035 -to 01:28:14.461 -c:v libx264 -crf 17 -b:v 1M -vf "subtitles=subtitle.srt,scale=-1:320,format=yuv420p" -c:a aac -af "pan=stereo|FL=0.5*FC+0.707*FL+0.707*BL+0.5*LFE|FR=0.5*FC+0.707*FR+0.707*BR+0.5*LFE" -movflags +faststart output.mp4” entirely from memory.My mentions right now.
-
R relay@relay.infosec.exchange shared this topic
