Hands up who saw that coming years ago…
BTW, a whole lot of people still have Amazon Echo devices at home. You know that little Internet connected puck thing with an always on microphone that transmits what it hears to an Amazon data center for voice recognition, so people can do things like control their lights, control their music, order stuff just by voice. I’m sure Amazon, the same company behind the Ring cameras, would never abuse that for spying purposes.
The original is a lot lamer than I thought it would be…
It lags for me whenever I access some filesystem that takes a while to respond. That could be a faulty or old device, or it could be an NFS share with multiple large file transfers going on in the background.
And when I say it lags, I don’t mean it just takes a while to show me a directory’s content, I mean the entire UI freezes and kwin will grey out the window because tha application isn’t responding any more.
This does not happen a lot, and if your file browsing is largely limited to a fast local storage, like a SATA SSD or even an NVMe, you may well never see this problem at all. But it does happen.
I think I know this meme template from somewhere, but I cannot quite recall from where. Could you give us a link to the original?
Okay, I’m generally on the side if dolphin UI-wise, but when it comes to the topic of lagginess, it has to be said that dolphin, and in fact, almost everything using the kio infrastructure, is the one shitting the bed here. You’d think a bit of multithreading will keep the UI from freezing up whenever the underlying I/O has some minor hiccup (which can absolutely happen in practice with network filesystems or USB sticks in combination with large file transfers), but apparently dolphin can’t do that.
If any person actually typed that they aren’t sane at all.
That doesn’t actually rule out anything.
War wohl nicht gut rüber gekommen, mein Kommentar sollte sein, dass Trumps Reaktion hier doch sehr an den Drachen erinnert.
Das glaub ich dir gerne so Leude Forza ist jetzt fertig runtergeladen woll‘n wa ma ne Runde starten
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.
I don’t even know which Linux specific fork you are referring to, it could be either a git fork or fork(2).