You can’t even assume those people are people. There’s a lot of bot powered disinformation out there.

“Why are you crying? Is it your haircut?”

The thing is, their anti-adblocking measures are still less unpleasant than actually watching ads.

WoW64 is a Windows subsystem for running 32-bit stuff on 64-bit Windows. You’re talking about Wine’s implementation of WoW64 - there’s the old one which needs 32-bit Linux libraries and the new one which doesn’t.

Also, if you want people to solve your issue instead of just guessing, we’re gonna need to see some logs.

port forwarding/firewall issues that most people don’t know how to deal with

This sort of thing makes me want to tear my hair out when I hear “Why bother rolling out IPv6 when IPv4 just WORKS!?”

NAT, port forwarding and the problems they cause are seen as expected, just the way the internet works instead of the dirty hacks they actually are. Most people aren’t old enough to remember the time when everything connected to the internet had a routable IPv4 address.

Personally, I’m on an electricity plan that gives me free usage at midday when solar is flooding the grid, so it’s useful for me to be able to charge as fast as possible in that window.

Faster charging is useful for more than just finishing before your next drive.

Because the “Why is the video being slow?” pop-up now sends you to the page blaming adblockers instead of the ISP shaming thing it used to do.

My phone will hotspot when it’s connected to WiFi. I can even tether it to a desktop PC and use it as a WiFi adapter.

That… really feels like something hardware should have been doing, but okay.

It generates an answer that looks correct. Actual correctness is accidental. That’s how you wind up with documents with references that don’t exist, it just knows what references look like.

Nobody wants to deliberately use the wrong compression type when extracting, so modern tar will figure out the compression itself if you just point it at a file. So tar -xf filename works on almost anything. You don’t need to remember which flag to use on a .tar.bz2 file and which one for a .tar.xz file.

“Hey, here’s a useful thing that I recommend to people: <your work>”

It’s basically a compliment

Maybe making progress during year three of your three day special military operation isn’t really something to celebrate.

Okay, but that’s still partially on Nvidia for refusing to participate. They could have argued for explicit sync early in Wayland’s development but they weren’t at the table at all, so they got stuck with the technology that was decided on without them and had to argue for changes much later.

And they started off arguing for EGLStreams, but it didn’t work well either. Explicit sync came later.

Wayland has a bunch of features that are so new they aren’t in the stable distros yet.

Nvidia went from declaring they were never going to support Wayland to trying to force their own EGLStreams stuff on everybody to reluctantly accepting the standard that was developed without them and trying to make it work for their driver. They’re playing catchup and it’s entirely their own fault for refusing to cooperate with anybody.

They’re moving more towards open source drivers now, probably because the people buying billions of dollars worth of GPUs to use on Linux servers for AI training have had words with Nvidia on the subject.

I’m not interested in my computer striking a balance between my needs and the needs of people seeking to manipulate me into buying things.

I paid for my computer, it serves my needs. Yes I do run Linux, how did you guess?

And then after everyone read the microcode bit and ran off to write articles, Intel added a note about the corrosion thing. It totally wasn’t timed that way on purpose.

I guess the people buying pallets of $50,000 cards have had words with Nvidia over their shitty closed-source Linux drivers. It’s not like Nvidia have suddenly decided to care about Linux gamers.