libytdl
A library written in pure nim for downloading YT videos. YT stands for "You're Turd!". Beat that RIIA!
!! WORK IN PROGRESS. NOT AT ALL IN WORKING STATE. Contributions welcome !!
Why libytdl?
- youtube-dl replacement: libytdl is aimed to be a replacement for yt-dl . That's it. But why replace at all?
- Dream big, start small: libytdl will for now start with only YT (You're Turd!) videos. Later it will move on to other domains!
youtube-dl's python problem
- fucking slow: Benchmarks with libytdl coming soon.
- No C API: youtube-dl doesn't have a C API. It is possible to have one but that's not "good practice". Having a C API means a library being language/platform agnostic. Nobody can fuck with C. Nobody! (in Alex Jones! voice)
- Its difficult to embed: Having a python based codebase means embedding will be difficult. At least relatively difficult with a C API. All languages have a C ABI.
- Python 2 problem: youtube-dl supports python2 meaning that every part of the development process has to cater to the old python version at least for now. This won't be a problem for youtube-dl in future though.
- Messy & old codebase: youtube-dl is a great project. but it has a lot of shit it carries with it. Go have a look yourself!
- DMCA Shit: youtube-dl suffers from the problem of DMCA/RIIA shit. Although this has been good these days, but libytdl will make sure the DMCA terms and conditions. Fuck RIIA! Fuck DMCA!
- Large executables: youtube-dl has to be used with a standalone python executable Since libytdl compiles down to native executable, the final executable sizes will obviously be smaller than the python version.
libytdl choosing nim over rust or go or c++
- Fuck Rust.
- Fuck Go.
- Fuck C++.
- Haskell? Lol!
- JavaScript, Python, Lua, Ruby, PHP? 2xLOL!
No more questions!
Language bindings for other languages:
Let me complete this library first!
Am I crazy or was I high when I wrote this?
Who isn't ?!