I'm curious what is the reason for a GUI for such a simple utility? The command line for this kind of tool seems like the perfect interface. Just copy a URL, paste it, press enter. No buttons to press, etc.
The number of people who might want to download something from Youtube & co is significantly larger than that of people comfortable with the cli.
> but
please stop gatekeeping
> motivated to learn about command line interfaces in order to use powerful software
many people never get basic tech literacy. i think we’d benefit from not simply assuming others have (or could have) access to the same resources, time and patience that we had. i think you probably mean well but your statement, which sort of implies that people say “I am choosing not to learn the important skill of using the command line!”, just comes across as ignorant and naive to me
You're replying to a tangential “continuing the conversation”-type comment as though it were a rebuttal in an argument. It already agrees with you.
Unnecessarily hostile. We need less of this.
I couldn’t care less how those zones are defined and configured, could be a configuration file for all i care, but the end result would be much more potent than copying and pasting into terminal and then making sure it’s quoted or escaped properly.
I’m a huge fan of good CLIs. I’m also a huge fan of GUIs. Why require people to learn something just to use a video downloader?
Even for people who know how to use the command line, most of us still spend the day in a graphical desktop environment, and having a program that integrates with that environment is very valuable.
From the screenshots alone some benefits are quite obvious. Namely the ability to handle multiple URLs at once, as also the Download-Manager with it's progress bar. I have a bunch of scripts myself for downloading videos, but interfaces for such things is not really a strength of the command line. I already thought about making some job-manager for myself because of those reasons. So I can totally understand people making a GUI and releasing it.
> The command line for this kind of tool seems like the perfect interface. Just copy a URL, paste it, press enter.
That's only if you have no other requirements. youtube-dl is a monster of parameters. You can setup any little crap and do many more things than just download a youtube-url. On the screenshot I see some config-buttons and some kind of profile? This quite matches with any mildly complex usecase for this tool. Having a GUI supporting you in setting up what other would do with scripts is beneficial, especially for those not breathing in shell-commands.
Unless you have reason to want something other than the default format that it will pick (perhaps for compatibility with an old set-top media box), or need other options like turning off SSL verification for some sites (it does much more than youtube) that have this misconfigured, options for playlist, ..., ...
For the simplest and most common use case it is just copy+paste, but for others there are a lot of options. I prefer the CLI and manpage myself, but some are far more comfortable with a GUI, finding the options more discoverable that way.
(though having had a quick look at the project page it looks like this doesn't offer options beyond format selection, but for some users that is useful enough to warrant a GUI)
The URL of this comment pastes like this, ready to be passed to commands:
https://news.ycombinator.com/edit\?id\=29069520 autoload -Uz url-quote-magic
zle -N self-insert url-quote-magic
autoload -Uz bracketed-paste-magic
zle -N bracketed-paste bracketed-paste-magic
It doesn't seem to escape $ (e.g. in <https://example.org/$PATH>), which doesn't inspire confidence…
Are there any equivalents for bash?
zstyle ':url-quote-magic:*' url-metas '*?[]^()~#{}=$'