Billegh

The concern was that it uses a “liquid metal” thermal interface, and that if the system overheated while vertical it could migrate away from the hot zones. This is a potential issue with thermal grizzly’s liquid metal product, requiring occasional maintenance. Apparently the ps5 doesn’t have that issue.

While the understanding would be nice to have, I suspect it is more a lack of backbone than anything else.

But 0x80 is how you’d normally express 128 as hex. So it’s relevant. But deliberately confusing.

And hopefully you never will

It was IBM’s binary to character transform. DB2 can still use it if you configure it to do so. Or was at least as of the version from 1998 that I had to replace.

I would have pegged EBCDIC for that, but ok

I sincerely hope that if they come up with a 128bit instruction set they call it “x80” to maintain backwards compatibility with previous set names and be deliberately confusing to everyone.

Sorry, not just implication; she was straight up talking about that.

I, for one, welcome our typography as flow control overlords.

Big fan of bash. Pretty sure it’s already installed for you.

I dunno, it looks like two framework laptops and a modern macbook pro. They could be doing far worse if that’s what those are.

Good job! ᕕ( ᐛ )ᕗ

You have to pacman -S femboy first.

We’d constantly get people by telling them holding alt and typing fax would get mirc to give them ops. Usually about a quarter of the channel would drop out.

For files, kebab case. For variables, snake case. For servers, megaman villains.

A little. If a third party cookie is set while you’re visiting a site, only that site will get the third party cookie back. Multiple sites can have embedded content making third party cookies, and with this change firefox will track where it was made and only give it back there.

With this change, it doesn’t matter if it’s first or third or whatever; cookies will only be given back to a site that matches much of what is in your location bar.

They really did do a good job. The difference is that they have access to documentation about Linux that wine doesn’t have about Windows.

Erectile Encumbrance

Right? I wish they’d respond like this when they themselves fuck up.

Because Wayland is fundamentally very different from the older X protocol, and many programs don’t even directly do X. They leverage libraries that do it for them. Those libraries are a huge part of the lag. Once GTK and Qt and the like start having a stable Wayland interface, you’ll see a huge influx of support.

A big part of the slowness is why Wayland is a thing to begin with. X hid a lot of the display hardware from apps. Things like accessing 3d hardware had to be done with specialized display clients. This was because X is natively a remote display tool. You can use X to have your program show its display somewhere else. Wayland won’t do that because that’s not the point. Applications that care will have goals for change. Applications don’t care will support it once someone else does it for them.

Right now, the only things that would benefit from Wayland are games and apps that make heavy use of certain types of hardware. Half of those don’t care about linux, while the other half is OK with X and xwayland.