Tux is my copilot, and never tries to be a back-seat driver.

Ah, so they just built the middleware, not a UI. That’s not what launcher typically means in this space, but fair enough. Thanks for clearing it up.

Anyone have screenshots?

It’s middleware for game launchers like Lutris, but specifically for Wine games. It uses GloriousEggroll’s custom Proton builds instead of stand-alone Wine/DXVK/etc.

Note that GloriousEggroll more or less discontinued his custom Wine builds, and has been encouraging people to use his Proton builds via this tool instead. It might make things easier or harder, depending on your needs and workflow. I expect it will be easier for casual Linux users when combined with a GUI.

And Perl both still exists and is actively maintained, so it “lost prominence” rather than “died”.

Okay, but you’re the one who called out “the demise of Perl”. Have you changed your mind? I was just responding to your question.

For what it’s worth, I think you were right about that: Perl is dead, in the sense of no longer growing or even maintaining the reach it once had. Other languages are overwhelmingly chosen for new code, while Perl has mostly fallen into disuse outside of people who learned it in its heyday and haven’t moved on, and irrelevance outside of legacy systems. It might not be quite as much a dead language as Latin (which also still exists and sees some use) but it’s well on its way there.

I see. You replied to me, though, with commentary that doesn’t fit the question I was answering or the thoughts I was expressing. Don’t you think it would have made more sense as a reply to OP?

Okay, but…

it’s clearly decided that Rust will be part of the future.

That’s not what OP asked.

If you think Zig still has a chance at overtaking Rust though, that’s very much wishful thinking.

That’s not what I said.

It’s too early to tell.

Rust has a killer feature and a tonne of buzz, but poor ergonomics.

Zig is developing into simple elegance and wonderful interop, but has more work to do before it will be widely usable.

It’s entirely possible that ideas and lessons taken from them will inspire another language that ends up eclipsing them both.

Isn’t exactly this kind of thing what is mostly responsible for the demise of Perl?

Perl died because better tools became available.

I think the WebView it uses on linux is webkit2gtk. I would expect that to be similar to Electron, but measurements would be better than guesses.

Does anyone know where to find unbiased, representative comparisons of memory usage between Tauri and Electron?

Source code mirrors, since the code is legal: (This is not a case of copyright infringement.)

https://git.naxdy.org/Mirror/Ryujinx

https://git.l7y.media/mirrors/Ryujinx

The commit hashes on both of these mirrors match the official ones at least until March 2024 (v1.1.1217). I can’t vouch for the more recent commits that extend through today (v1.1.1403), but the two mirrors do at least match each other. Another user has confirmed that these hashes match his clone of the official repo through 2024-09-24.

Warning: A zip file in the ryujinx_202410 subdir of https://archive.org/download/ claims to have the full git history, but the hashes do not match the original source repo. It’s possible that the mismatch is an artifact of some accident, rather than malice, but I would avoid it just in case.

Reminds me of a recent Disney case:

https://www.bbc.com/news/articles/c8jl0ekjr0go

It bothers me that we as a society continue to surrender our agency, our rights, and even our well-being to whatever restrictions a corporation makes up to benefit itself, just because they’re in a (practically unavoidable) terms & conditions document.

It’s getting so bad that people sometimes mistake corporate policies for law, crying “that’s illegal” if someone steps outside the bounds of a software license.

Adding insult to injury, enforcement of these things is paid for by us, through taxes.

I think it happened more than a few years ago. US citizens might want to see about overturning Citizens United.

Much like the way we were told for ages that a glass of wine every day was good for our health. I think the latest research is showing no evidence of that, but rather that any amount of alcohol raises the risk of cancer.

I continue to be impressed by how far we’ve come in algorithmically imitating forces of nature. If you like this stuff, have a look at the EmberGen demo clips

I suppose I would avoid connecting to untrusted networks, or avoid opening print dialogs while on them, or uninstall CUPS until a fix is available.

Even the Linux kernel / Linux Torvalds are moving towards Rust.

No, they aren’t. They are experimenting with it in certain new device drivers. No move is planned, and it’s too early to tell whether there will ever be one.

That refers to the fact that printer advertisements can contain lies: When you see a familiar printer name appear on a network, it could always be an impostor secretly pointing to the address of a malicious device.

So my first advice stands: Avoid interaction with untrusted or potentially compromised print servers.

To be clear, when I say “interaction”, I don’t just mean printing to them. I mean any interaction at all. Even just browsing a network for printers could potentially mean your system contacts the devices at the advertised addresses, and receives data from them. This Qualys report doesn’t make clear whether this kind of interaction is safe, so I have to assume for now that it is not.

Exploitation involves sending a malicious UDP packet to port 631 on the target, directing it to an attacker-controlled IPP server.

Okay, so at least until this is patched, it would be a good idea to shut down any CUPS-related process that’s listening on port 631, and avoid interaction with untrusted or potentially compromised print servers.

Either of these commands will list such processes:

$ sudo lsof -i :631

$ sudo fuser -v 631/tcp 631/udp

I don’t want to diminish the urgency of this vulnerability, but it is worth noting that “affecting all GNU/Linux systems” does not mean that every affected system is actually running the vulnerable code. Some installations don’t run print services and don’t ever communicate with printers.

Also, I suspect that the author’s use of “GNU” in that warning is misleading, potentially giving a false sense of security. (Sadly, a certain unfortunate meme has led many people to think that all Linux systems are GNU systems, and the author appears to be among them.) I don’t see any reason to think musl builds of CUPS are immune, for example, so I don’t assume my Alpine systems are safe just because they are not GNU/Linux.