Gimp devs will have to port it to Gtk 4 before rewriting it in Rust, because Rust Gtk 3 bindings are now obsolete lol.

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.

I combine it with blocking users. Political communities are blocked entirely, and then users who post irrelevant political crap in non-political communities are blocked individually.

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.

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.

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.

I’ve got a problem with port forwarding I can’t get working, never had that problem before and I don’t know network stuff well enough to figure it out.

Docs says that CachyOS has UFW firewall enabled by default. You can search how to configure it, it seems quite easy.

The updates are the winner for me- I don’t know how long this has been a thing with arch but downloading multiple packages at the same time. Game changer. I love Tumbleweed, but a 2gb “zypper dup” downloading package by package could take me 30 - 60 minutes.

It’s usually the issue with automatic mirror selection. If you interrupt zypper using ctrl-c (only when it’s downloading, not installing of course) then it should select a faster mirror next time you run it. Zypper devs really should work on this though.

I actually installed it recently out of curiosity, but I’m hesitant about learning its advanced features like that. At least jq is a standalone tool that’s more ubiquitous than nushell, so you can rely on it even in environments that you don’t fully control (e.g. CI like GitHub Actions). And if you use it in some public code/scripts then other people will be more familiar with it too.

Fish is a replacement of bash that’s a bit more user friendly (has some cool auto completion features out of the box and more sane behaviour like handling of spaces when expanding variables). I personally started to use nutshell recently but unlike fish it’s very different from bash.

Starship is a “prompt” for various shells (that bit of text in terminal before you enter the command that shows current user and directory in bash). I haven’t used it but AFAIK it has many features like showing current time, integration with git, etc.

I use it occasionally but every time I need to do something a tiny bit more complex than “extract field from an object” I have to spend half an hour studying its manual, at which point it’s faster to just write a Python script doing exactly what I need it to do.

Even if a file manager doesn’t have this feature, you can probably get around that by adding a new .desktop file in ~/.local/share/applications that accepts specific MIME type and runs a script on “opened” files.

https://forums.opensuse.org/t/snapshot-start-up-slowdown-18112024/180434
https://bugzilla.opensuse.org/show_bug.cgi?id=1233532

https://forums.opensuse.org/t/after-todays-upgrade-tumbleweed-i-can-no-longer-log-in-via-the-wayland-session/180541
https://bugzilla.suse.com/show_bug.cgi?id=1234302
https://gitlab.freedesktop.org/mesa/mesa/-/issues/12253

Not all hardware seems to be affected (at lest in case of second issue). I have a AMD GPU though and I hit both of them.

Latest Tumbleweed snapshot has a Mesa bug that causes 50% chance of black screen after login. A few weeks before that Plymouth was broken causing >1 minute boot times. To solve these issues users need to learn how to rollback updates from command line, so it’s certainly not a good replacement for Windows.

I know it’s rolling release distro but you can’t claim “it’s rolling release so bugs are expected and it’s your fault for using it” and “it’s betest and stablest system ever, everyone should use it” at the same time.

Not quite true. Code still has copyright owners and they are not bound by terms of free software licenses (they use licenses to allow other people to use their code). This means that copyright owner can make their code proprietary at any time, or change the license to any other. Although they can’t do anything about previously released versions AFAIK.

However in case of projects with many contributors that don’t have a CLA (which transfers an ownership to some organization) nothing can be changed in practice since every contributor owns their piece of code and will have to consent to the change of license. Linux is such a project so it will forever remain GPLv2 licensed.