budgie-desktop VS yt-dlp

Oh yeah, no. Multiple entire desktop environments with significant popularity (Cinnamon, MATE) owe their existence today to how universally hated GNOME 3 was, and how obstinant and intolerant the GNOME developers were towards differing opinions that challenged their "vision".

In fact, the same thing is sorta playing out even right now with GTK4 and other GNOME stuff, though I think with somewhat less public spectacle but arguably even larger development efforts behind it:

https://joshuastrobl.com/2021/09/14/building-an-alternative-...

https://www.theregister.com/2021/11/08/system76_developing_n...

https://blog.system76.com/post/closing-in-on-a-cosmic-alpha

https://github.com/BuddiesOfBudgie/budgie-desktop/issues/141

https://medium.com/@fulalas/gnome-mess-is-not-an-accident-4e...

Other editions of Solus use Papirus icons (https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/releases), and the Budgie project created its own menu icon recently: https://github.com/BuddiesOfBudgie/budgie-desktop/blob/main/data/icons/actions/budgie-menu-symbolic.svg

Budgie might be worth checking out (I've used it on Manjaro): https://github.com/BuddiesOfBudgie/budgie-desktop It was extremely responsive on a 2009 laptop.

Otherwise whatever AntiX and Puppy use, which are mouse-driven UIs, are probably lower-resource than Budgie.

Budgie

This is the way: https://github.com/BuddiesOfBudgie/budgie-desktop/wiki/Budgie-Desktop-on-Fedora

You might try asking at their official GitHub page or read thru the wiki there and see if it gives some info.

You claim that Solus doesn't have any, but the budgie desktop has over 70 different contributors. https://github.com/BuddiesOfBudgie/budgie-desktop/graphs/contributors

I just learned that the Budgie Desktop is written in Vala.

https://github.com/BuddiesOfBudgie/budgie-desktop

Also, on Arch I use Pamac as a GUI for package management and it is written in Vala as well.

I have used apps for quite a long time before realizing they were written in Vala. Not great for marketing but otherwise I would consider that one of its strengths.

You can put these options in a config file and they will become the default: https://github.com/yt-dlp/yt-dlp?tab=readme-ov-file#configur...

Yep. yt-dlp and youtube-dl

https://github.com/yt-dlp/yt-dlp

https://github.com/ytdl-org/youtube-dl

Will also start to feel the impact. My theory is that we will see a bunch of new video hosting sites as youtube itself attempts to lock down its ecosystem. They haven't paid attention in any adversarial way as far as I can tell.

When they do, it wont be great.

The points you make aren't unreasonable.

It is necessary to establish clear boundaries of what can and can be provided by the maintainers. If not done at an earlier stage of the project, the support burden becomes too much to bear at which point the maintainer transfers ownership, and the project suffers from catastrophic consequences such as the xz backdoor we're talking about here, or other cases where the project mostly stalls and serves as an ego-boosting platform for the new maintainer, as was the case with PhantomJS[6].

This can also happen in your life, where a "friend" sees that you possess a certain skill, and then gradually tries to push an inordinate amount of their personal work related to this field onto you.

Personally, I think it's best to use an approach with extremely clear communication as to what the maintainer can and cannot provide. This can be seen, for example, in yt-dlp[1], where the consumer is clearly informed upfront that not providing detailed information as requested will lead them to block said consumer; or sqlite where their position regarding contributed patches[2] and support[3] is similarly made clear.

Having a shouty BDFL like Torvalds can also help improve code quality[4] and questionable contributions[5], though it is better that the shouty BDFL makes statements that are professional and do not show as much aggression; so for example, "Mauro, shut the fuck up"[7] would become "Mauro, your response is completely unbecoming for a Linux kernel maintainer, and is not in line with the promise of not breaking userspace."

[1] https://github.com/yt-dlp/yt-dlp/issues/new?assignees=&label...

[2] https://www.sqlite.org/copyright.html

[3] https://www.sqlite.org/support.html

[4] https://www.theregister.com/2024/01/29/linux_6_8_rc2/

[5] https://cse.umn.edu/cs/linux-incident

[6] https://github.com/ariya/phantomjs/issues/14541

[7] https://lkml.org/lkml/2012/12/23/75

Or just "yt-dlp "

yt-dlp ( https://github.com/yt-dlp/yt-dlp ) still works pretty well at the current state of Twitter.

To download audio from YouTube videos, you'll utilize the widely used yt-dlp library, which can be installed using the pip command as follows:

Use: `yt-dlp with --write-comments --no-download --batch-file FILE`

- FILE is a text file with a list of YouTube id's/URL's

- https://superuser.com/a/1732443/4390

- https://github.com/yt-dlp/yt-dlp

> Then youtube-dl wasn't a thing anymore (maybe it is again?)...

yt-dlp is definitely a thing: <https://github.com/yt-dlp/yt-dlp>