

For me in Plasma 6.3.2 it has noticably different font rendering compared to 100% scale with increased font size. Text looks thinner than it normally should. It’s probably the consequence of downscaling.
For me in Plasma 6.3.2 it has noticably different font rendering compared to 100% scale with increased font size. Text looks thinner than it normally should. It’s probably the consequence of downscaling.
Too bad fractional scaling is still not universally supported. In Firefox it’s buggy and disabled by default (and pretty much abandoned), and using default compat mode (when app is rendered at nearest greater integer factor and then downscaled by compositor) has some strange font rendering issues and potentially worse performance (on 4K monitor the resolution Firefox would be rendering itself would be humongous).
Thankfully in my case I can just increase font size and it works much better than with fractional scaling.
This for whatever doesn’t work on openSUSE Tumbleweed, last time I checked.
All POSIX compatible shells have their quirks and differences because the common POSIX part is rather small, so you will need to learn them anyway when switching from one to another. Fish is not that different from them (to much less extent than something like nushell) and it benefits from having less ancient baggage.
If a messaging service requires a phone number then it’s not “secure” lol.
IIRC this extension just doesn’t work in Flatpak. You need to use Firefox outside of the sandbox, installed via package manager or official build from Mozilla.
Haven’t used GNOME for a while, but I guess that’s a problem of open source projects in general. Though GNOME at least has Red Hat behind it.
I don’t think Fedora has a “stable” channel. It has “testing” repo from which updates are pushed to “updates” repo after approval, and that’s it. My understanding is that ublue’s “latest” channel follows Fedora’s “updates”, while “stable” seems to update weekly (though it’s unclear what happens if a package update arrives in Fedora just before “stable” image is about to be built)
Does it use the same flawed approach as Manjaro by indiscriminately delaying all updates (including critical security fixes)?
Fedora is a bit too eager to deliver new updates IMO, especially KDE. As much as I love KDE, their .0 releases have had serious bugs several times in a row now. It’s always better to wait for .1 patch with Plasma. It may be hard for the user to break Kinoite, but it won’t save them from bugs.
Fedora’s mission have always been to push new stuff when it’s “mostly ready” at the cost of inconveniencing of some users, so I wouldn’t recommend it for non-tech-savvy people.
I know people say that it’s 100% stable for them (as they do for Arch, Tumbleweed, Debian Sid, etc) but that’s survirorship bias. As any bleeding edge distro, Fedora has its periods of stability that are broken by tumultuous transitions to the new and shiny tech (like it was with Pipewire, Wayland default, major DE upgrades, etc). During these times some people’s setup will break and you don’t know ahead of time if it will be yours.
You can still install RPMs through dnf. There is also dnfdragora AFAIK. Packagekit (cross-distro API and daemon that abstracts package managers like dnf and apt) is a pile of crap anyway, and is a source of many GNOME Software’s issues.
It does. This discussion is about Fedora where packagekit works with dnf and RPMs.
Not just synonymous, it the official name of DE itself.
Everyone who have use Twitter in the past 2 years is a nazi.
Arm is insanely fragmented, every device must be have dedicated drivers and hardcoded specific configuration in the kernel. And sometimes even separate kernel builds. Also Snapdragon X devices are not even fully supported upstream in the most recent kernel yet. Which means they are many years away from being supported in Debian. Unless someone makes a fork of Debian with latest kernel and not yet upstreamed Qualcomm specific patches (which how these “arm distros” are usually made).
It’s mirroring micronews.debian.org, not Twitter.
That’s the other way around. It’s an OpenGL driver that uses Vulkan under the hood. OP would need the opposite to have Vulkan on his card, but I don’t think it’s possible given that Vulkan is a lower-level API compared to OpenGL.
Well, login gating worked for Facebook, Instagram and Twitter (it’s not dead yet despite some people’s claims). We here are tiny minority of social media users.
They are currently A/B testing blocking access to videos without an account. That’s why some people are getting errors. It’s likely that it will be rolled out to everyone in the future.
Gimp devs will have to port it to Gtk 4 before rewriting it in Rust, because Rust Gtk 3 bindings are now obsolete lol.