Jia Tan liked your comment
Without the traditional distribution workflow […]
You are aware that the xz exploit made it into Debian Testing and Fedora 40 despite the traditional distribution workflows? Distro maintainers are not a silver bullet when it comes to security. They have to watch hundreds to thousands of packages so having them do security checks for each package is simply not feasible.
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.
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
Note that the people behind the Asahi don’t yet recommend getting a MacBook for the sole reason of running Asahi on it.
ngl, I’m annoyed whenever someone creates an application but doesn’t want to publish their code cause it looks bad. Like no one cares that your code is bad and by publishing it, you can get others to help you improve it.
This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.
It’s like when an intern accidentally drops the production database. It’s not the interns fault for sending the wrong command. It’s the managements fault for not restricting access in the first place.
Also, you can just download an older version of the toolchain and use that to compile the project. If the project is properly setup it’ll tell you the toolchain version it used. If not you can probably guess by the time of the last commit ^^
Aren’t AppImages still limited to Xorg?
Also there’s no centralised update mechanism or dependency deduplication, no?