I wonder if that means it could be combined with DXVK to enable support on older DirectX versions as well. ^^

The easiest way to block an auto-upgrade to Win11 is to just disable TPM in the BIOS. That way Windows will see the PC as not Win11 compatible and not perform the upgrade.

Looks interesting, I’ll check it out, thanks :D

YAML would such a nice language for config files but then it turns out that “no” is falsy and so a list of Scandinavian countries turns from

• se
• fi
• no

into

• “se”
• “fi”
• False

I wish there was like a JSON5 equivalent for YAML that just reduces its scope lol
(and no, TOML also looks ugly :P)

We should probably update this post given that vanilla is now playable ^^

The linked message is from 2019, i.e. per-M1 Apple laptops and at a time when arm in datacenter was just starting out.

Tbh, I feel like it’s kinda pointless to discuss a comment made by someone over 4-years ago. Both the environment and the person itself can change a lot in that time.

I feel that at the very least, the customer in that case should be entitled to a complete refund of the product, regardless of whether they bought it 5 days or 5 years ago and regardless of the condition their device is in.

This should at least give some incentive to companies to not perform such sweeping changes to their terms of service and if they do, the customer can more easily remove themselves from the lock-in without taking a financial hit.

Or just use long-forms like

tar --create --file pics.tar ./pics

instead of

tar -cf pics.tar ./pics

or

tar --extract --file pics.tar```
instead of

tar -xf pics.tar

which is honestly way easier to remember... \^\^

So basically it’s just another GNOME release gotcha.

AFAIK, the extension developer needs to explicitly set each version of Gnome they support. Even when the Gnome version doesn’t have any breaking changes, the extension developer still needs to update their extension to enable their extension for the new Gnome version.

On that note, screen sharing worked just fine for me on Wayland Fedora 38 with Zoom Flatpak.

Convenience for end-users and avoiding link rot is probably one of the reasons.

So far, Fedora has been rock solid for me ^^

“X post” kinda also refers to “crosspost”. I’d suggest to instead use “Twitter/X post”. Otherwise, keep up the great work <3

I just really dislike the whole left/right tribalism. Politics is a lot more complex than left/right and just marking someone as either just increases polarisation…

As someone running a Framework 13 with Fedora 38 with 1.5 fractional scaling using Wayland I cannot say I experienced the same issue. Everything kinda just worked out of the box.

Personally I couldn’t go back from HiDPI screens. The lower resolution just makes stuff look blurry IMO.

yeah, tunneling into your local network and then calling WoL from there is the way to go.

Yup, this. Started update via Gnome Software, walked away from my laptop to make some coffee, restarted when I came back and it was done. ^^

Fedora has a KDE spin and gets some updates faster than even Arch (e.g. new Gnome releases) while also being considered stable. Heck even the the Asahi Linux project switched from Arch to Fedora as a base recently.

If you really need something from the AUR you can just use distrobox to generate an arch container and install the AUR package in there. You can then export it from distrobox to your application list with a single comment so that the fact that it’s running inside distrobox becomes completely transparent.

That way you have a stable but up-to-date base while also still having access to AUR.

That being said, in my 7 years on Linux I never needed something that was only accessible in AUR but maybe that’s just me ¯\_(ツ)_/¯

Been using the PoC extension for a few days now and I’m absolutely in love with it <3

Also why having doc comments and docs generated from code are super useful. When someone changes the code but not the comment above, it becomes really obvious that something was missed as opposed to having code and doc changes be two separate tasks.