How do you refill the tanks, how loud is it for bystanders, and what happens if you stand too closely behind?

Mechanical Turk. Operators are overseas and take over as needed.

It's not real.

People misunderstand what is going on. It's not the OS itself, but all of the additional features that get installed and run automatically that cause the problem. Not everything requires printer support, but yep, it's there and enabled by default. The ability to change desktop wallpaper, or sounds, or all of this other stuff, it's in there. Translucency of UI elements, this and that, it adds to how much RAM is getting used.

While you can really cut back on all the stuff that SHOULD be an optional feature, the fact that your typical user doesn't know what they might need or not need makes it so turning stuff on by default makes a lot of sense, right up until you run out of RAM.

All the mice I use are hardwired.

Still waiting on my $39,000 cyber truck that is bulletproof and floats.

So, throw the little thugs in a jail for a few weeks where assaults are known to happen, and see how THEY like to be assaulted.

Maybe it works now or there is some suitable replacement but I never bothered as I don't see what problem Wayland is trying to solve and I don't need a faster screen.

Wayland isn't faster either.

The problems Wayland fixes primarily are ones where anything it its responsibility. All the functionality that worked in X basted systems but not Wayland based systems is not a problem you see because Wayland is just a protocol so it's not Wayland's fault (though this reasoning never applies to X which is also just a protocol), or out of scope for Wayland (so it's not Wayland's fault).

Oh but because the compositor is now not a separate process there are two fewer task switches between for each keypress so Wayland does genuinely save a few hundred nanoseconds of CPU time per keypress. Well, it doesn't because it's just a protocol. It allows a sufficiently well written compositor to save you a few hundred nanoseconds per keypress compared to a comparable X based one...

If you run X, you can restore this functionality

Fear not friend, they are trying to close this loophole too.

Oh, this has been a problem since at least Windows 7, and it probably originated with Vista. It's the first thing I noticed after updating from XP, and it's been driving me batty on ALL my machines, regardless of hardware configuration, for well over a decade.

There's a LOT of responsiveness issues associated with the WDM. Thankfully missed input events only affect desktop applications. Anything that runs in fullscreen or overlay mode works fine.

I appreciate the tip, but I get seriously annoyed when geeks jam "it's trivial" or "it's incredibly easy" into every conversation. Please don't do that.

A microsecond here, a nanosecond there, pretty soon you're talking big time. Now think about it, if you're off by a few milliseconds in terms of the Earth orbiting the galaxy at 515,000 mph that's probably tens of thousands of miles (you do the math, I'll do the implications) .. Now let's assume Jesus had planned to come back on say January 14th, 2100 AD. Where the fuck would the Earth be at that time? Since we didn't account for the microseconds and all that .. the Earth would be like thousands of miles off its actual predicted position.

It's never the right time to wrong time.

Yes, most was a poor choice of words. More accurate we cant live without it. Wonderful thing about water is it's utility, I can drink it, break it down into H2 and O for fuel and O to breathe. Why we are so keen to find it. I fully expect you know that ;)

Thank you for exploring the idea with me, a pleasant distraction from the work I should be doing.

I don't know it seems to work for Donald Trump and you voted for him. Which was a neat trick since you're in Russia. Just out of curiosity are you working from home since Ukraine blew up your data centers?

Bill Gates should have been taken more seriously .. like think about it .. how the hell is 8 BILLION bytes not enough???

Up until, I would say the 90s .. we used to view RAM as a precious rare mineral allocated to us by God. Every bit had to be accounted for. You didn't just go allocating memory willy nilly. You can't be like malloc this, malloc that, as if you own the place. Every bit and byte and to be mulled over. You'd think "do I really need to use an int? perhaps byte or maybe even a boolean would suffice?" Sometimes you'd have to compromise "I really need a double here, but fuck it, all I have is two booleans" That's how we dealt with shit. Contrast that with you Gen Z fuckers nowadays who are like "hmm, I need to store an on-off state .. let me use an entire JSON structure embedded in an HTML file!"

You know what, fuck all of you!