61–70 of 95 posts
Youtube-dl is one those things I wish could stay under the radar.
youtube-dl being more known isn't that hazardous, as long as there's a community of people ready to confront the latest ballast sent to make people's lives more miserable - which there is so far, and I'm honestly incredibly grateful for that.
Jesus .. the package.json alone is probably longer then a shellscript would be that implements the same functionality.
This tool probably works anywhere node runs and the author didn't have to think about that, during the evening they took to write it.
Earlier quoted context omitted.
I would love to see the shellscript equivalent! :))
For videos, this should work... added to your .bashrc file, which then needs to be reloaded (only once) by typing source .bashrc in your home directory from the command line: alias yt='youtube-dl --recode-video mp4' On my system I have a funky python setup so I need to use this instead: alias yt='unset PYTHONPATH; youtube-dl --recode-video mp4' I don't see the need for interactivity because the only format I ever wan…
Then this tool isn't for you. If you're gonna skip the whole point of the tool, you can't claim your code suggestions are equivalent.
Earlier quoted context omitted.
Don’t see why, if anything more people should know about it so shared content can become more redundant as people download it across the world. YouTube is a fairly brittle hub sometimes with all the takedowns.
I suspect the GP is concerned Youtube will take steps to block it. This scares me a bit too, I watch basically all Youtube content via Youtube-dl. I have a script that runs every night on Mac, so that new content automagically appears in my Movies folder.
It automatically places videos in the configured folder based on type. Just type in an artist name, and select the type of video. Saves me a ton of time.
It's easy to extend and I plan to generalize it and translate it to bash sometime soon. I just do all of my media consumption in Windows currently.
Earlier quoted context omitted.
Sure, the the node code uses fewer lines than the Go code. But what you’ve failed to notice is the Go code calls APIs directly rather than fork()ing and does so within its own code base (how many lines of code is in the countless imports of your node example?). Plus the Go code also has unit tests which the others don’t. Line numbers are always a terrible metric for proving anything but in this case your especially a…
In absence of more accessible complexity measurements, line counts do matter somewhat. E.g. the briefer a program is, the more readable it is (last time I checked, brainpower and time is much more expensive than computing power and bandwidth.) The Node example has zero external dependencies outside of the Node.js standard library.
All of your stated benefits are nice for the maintainer but mean little to the end user. This gushing praise for Node reads like nobody has ever built elegant CLI apps until Ryan Dahl turned of age and put JS on a server.
Earlier quoted context omitted.
I suspect the GP is concerned Youtube will take steps to block it. This scares me a bit too, I watch basically all Youtube content via Youtube-dl. I have a script that runs every night on Mac, so that new content automagically appears in my Movies folder.
Meh, you can never truly block it out. There will always be a way so long as you can actually see a video on your screen.
Earlier quoted context omitted.
I suspect the GP is concerned Youtube will take steps to block it. This scares me a bit too, I watch basically all Youtube content via Youtube-dl. I have a script that runs every night on Mac, so that new content automagically appears in my Movies folder.
would love to know more about this. do you just download new videos from your subscriptions? what sort of script? can you share it? :-)
Fair warning, it’s quite macOS specific.