This is x86 assembler. (Actually, looking at the register names, it’s probably x86_64. On old school x86, they were named something like al, ah (8 bit), ax (16 bit), or eax (32 bit).) Back in the old days, when you pressed a key on the keyboard, the keyboard controller would generate a hardware interrupt, which, unless masked, would immediately make the CPU jump to a registered interrupt handler, interrupting whatever else it was doing at the point. That interrupt handler would then usually save all registers on the stack, communicate with the keyboard controller to figure out what exactly happened, react to that, restore the old registers again and then jump back to where the CPU was before.

In modern times, USB keyboards are periodically actively polled instead.

https://www.youtube.com/watch?v=cNAdtkSjSps

Why does nobody mention the Discordian calendar? 5 days per week, 73 days per month, 5 months to a year (Chaos, Discord, Confusion, Bureaucracy and the Aftermath). On leap years, it adds one additional day (St. Tib’s day) with a name but no numerical date.

Who’s Rich? Did you mean Randall?

Why the fuck is a Microsoft account so important to Windows that running it without one is considered a “loophole”?

Files and directories starting with a dot are hiden by default. You are aksing for this stuff if you manually unhide them.

There’s that “I never vote because politicians do not care about the issues of people like me anyway” attitude again.

(Hint: They don’t care because your kind won’t vote anyway.)

S-ATA still is the only way to have more than two drives in the system.

IMHO, it was a mistake to make USB block storage use the same line of names also used for local hard disks. Sure, the block device drivers for USB mass storage internally hook into the SCSI subsystem to provide block level access, and that’s why the drives are called sd[something], but why should I as an end user have to care about that? A USB drive is very much not the same thing for me as a SCSI harddisk. A NVMe drive on the other hand, kinda sorta is, at least from a practical purpose point of view, yet NVMe drives get a completely different naming scheme.

That aside, suggest you use lsblk before dd.

I do not trust any “livability” statistic that lists Frankfurt as the most livable city in Germany.

Also, the chart does not give its selection criteria. Medium sized cities to cities on the smaller side are completely missing. I get not including towns, that would overwhelm the graph.

Then again, what even is a city, what sets it apart from a town? Different regions in Europe have vastly different definitions of that, with the UK’s definition being particularly notable for how useless it is.

deleted by creator

Using “they” when you haven’t yet established the group you are referring to in context feels weird and kinda wrong, especially if it’s about a group of inanimate objects. It really looks like the word should have been “there”, but they just mistyped and then didn’t catch the error in the editing process or didn’t bother to correct it.

That’s what I think is wrong here. I’m not 100% sure that this grammatically wrong, but it sure feels like it. Might depend on what the page before this one said.

I also wondered for quite some time why my Logitech C920 webcam seemed to be using much lower framerates (which could be perceived as “laggy”) in Linux as compared to Windows. It turns out it was transmitting uncompressed YUV frames by default, and for that, the bandwidth of my USB port just wasn’t enough. (Maybe in USB C it would be enough, but this webcam isn’t USB C.)

It worked like a charm after I manually set the format to H.264 in OBS. (“Like a charm” meaning it was transmitting 1920x1080 at 30 fps.) Unfortunately, I don’t know how to do that in an application-agnostic way, but maybe someone else here can enlighten us. Worst case, install https://github.com/umlaeute/v4l2loopback and pipe your webcam stream through OBS…

I think it’s possible that this is the same problem that you have run into.

Graphics workloads are GPU bound.

This isn’t a graphics workload, or at least not that kind of graphics workload. The GPU is irrelevant here.

As far as I know and could look up on short notice, libx265 does not make use of GPU computing (via CUDA or otherwise), so the answer to your second question

Would tight integration between amd cpu + gpu help in this case?

is almost certainly no.

Performance wise, the ffmpeg command you posted will be completely dominated by the video encoding part through libx265, to the point where everything else is pretty much negligable. Also, the rest of this does not use gpgpu computing either.

In F/OSS, it is not unusual for software to stay below 1.0 version for a long time yet still get a lot of use. Just look at how long OpenSSL, for example, was at 0.9.something, while already being of crucial importance to a lot of internet infrastructure.

The reasons for this are varied, but the most important is probably simply that free software developers don’t feel the pressure to call a product 1.0 when they don’t believe it is ready to be called that.

This must be the home decorating equivalent of “everything louder than everything else”.

Pipewire makes me feel like I’m a bit stupid. I keep reading about it, I read the introduction and FAQ on their website, yet I still couldn’t tell you what that thing even does. All I know is it’s a slightly less buggy drop-in replacement for pulseaudio, and pulseaudio is something I use because Firefox forces me to. (I would still be on plain old ALSA if it weren’t for Firefox.)

Also, it definitely did not “just work” for me out of the box, I had to do quite some digging and some very non-obvious stuff to get it to a) start up and b) let me use my microphone. I still don’t even know what “starting up” really means for pipewire (is there a daemon or something?), the website likes to pretend that isn’t a thing, but without doing some stuff to start it up, audio just won’t work for pulseaudio and pipewire applications…

I don’t think the problem with that one is the photography…

Some of those Cons sound pretty bad, especially the graphics problems. A lot of those I figure I could live with, but some, like the constant noise on the graphics or a low-quality touchpad would be just too much to tolerate.

I am currently awaiting my (pretty damn expensive) Framework 16 at this time, and I can only hope my experience will be a bit better than yours…