Thanks for this, I was wondering why Linux was using more power (on my UPS) compared to Windows.

I just added amd_pstate=passive to grub and it brought it down ~15 watts, there’s other options but I believe they require kernel 6.3 or higher. More info here.

Also I was using this before but for other people, if your it87 based sensors aren’t showing up, frankcrawford maintains an updated it87 module.

With kernel 6.5+, the default is now amd_pstate=active for Zen systems.

I recommend amd_pstate=guided for 6.4+ though as at least on my machine, this seems to yield the best performance/energy trade-off.

Fan curves are easy. Set them to always run at 100% and put on a noise canceling headset.

Another thing that’s satisfying is having a machine that knows when it needs to turn on the fan and never needing my input, which would be pretty ignorant on the subject anyway.

Serious person here.

Can autocomplete fill in a YouTube URL or Spotify playlist name? Can I browse the list of what’s available and filter, drill down, poke around according to my whimsy?

Or if I’m accessing a local file, how do I find that one video of my cat named VID-004326.MP4?

Can I autocomplete the parameters themselves, which are betimes lengthy and unwieldy to type out?

Even if it’s possible, and I’ve mastered every arcane parameter necessary to do it, is it really faster / more convenient than doing it through a GUI?

Maybe there are good answers to the above questions—I don’t know and would love to find out—but they and many more like them are surely reasonable and far from meme-worthy, or else I’m missing something huge.

presses tab

Woa, dude!

looks like it is using DLP backend, didn’t read the whole error

[ytdl_hook] ERROR: [youtube] BBJa32lCaaY: Unable to extract uploader id; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
[ytdl_hook] youtube-dl failed: unexpected error occurred
Failed to recognize file format.

Let’s hope youtube hasn’t finally ground the project permanently

deleted by creator

It very highly depends on the application

For something used daily that’s more or less true

For something that needs very complex configuration like specific ffmpeg transcoding rules and cmake build files - you’d have menus that are 5-10 pages long and full of super detailed selections and forms, while in reality you’d only want to switch on or off one thing, so it would be easier just to write the command

When I made my small game engine I had a second window full of settings that I could change dymamicaly. After like 2 months of work it was so full of settings it was very hard to navigate even with all subdivisions and layouts properly made

Also, GUI apps often lack specific or new settings for the terminal app they’re built on

now a three headed demon has appeared and eaten your neighbour alive.

Reminds me of … (a bit on the long side, but i’d say worth the read, if you have some time)

… I’d still watch it.

I have no problems with small man pages. My problems with manpages arise when a command has hundreds of arguments and I need to find a very specific combination.

That’ll be useful for a swap partition, but if you’re using a swap file instead of a partition it won’t work.

To clarify, a swap file is just a file on your hard drive the size you’d like your swap to be. Filled, at the start, with zeros. You still put it in your fstab to mount it but instead of a full partition, it’s just a file.

This makes it more flexible, and easy to change the size of or turn it off or on during operation, safer to change the size (less steps, less ramifications, lower chance of data loss), or have it expand as needed, but is more restrictive in other features while being a bit slower and less secure.

Windows has a similar system for swap called a pagefile.

On linux, while there is a gui to change a swap partitions size, changing the swap files size has no gui. Even though it is, theoretically, a simpler operation. Simply run swapoff, delete the old file, create the new file, run swapon. No partition managment needed, essentially no chance of data loss

I wrote a couple hundred lines of it as part of my apprenticeship a few years ago and have occasionally needed to deal with small scripts since then.

In principle, I like the idea of static typing, as I’m a backend dev, but yeah, I don’t particularly want a script to ever become large enough where static typing truly becomes useful.
I would strongly recommend using a full-fledged programming language instead. In particular, because Microsoft somehow managed to make Powershell feel even more verbose than even C#, which is one of the most unnecessarily verbose languages out there.

Back then, it also felt quite like a web technology, where many features were only available, if you had the right version combination of Windows, Powershell and .NET installed.

And of course, the biggest strength of Bash is unattainable, which is that there’s multiple decades of people posting snippets and example commands online.

Having said all that, maybe for Ops folks, who *have* to script a Windows configuration and aren’t proficient in any proper programming languages, it is genuinely quite useful.

There is zero time to be saved…