We still don’t know how much of Oblivion they actually recreated, considering it’s rumored to be made in UE5 which is a completely different engine. I’m most worried about open world and “immersive” elements such as Radiant AI and NPC schedules, proper wildlife AI, etc.

I honestly did not expect Starfield to have actual flyable spaceships and vehicles. That was a pleasant surprise, so Bethesda evidently has not stagnated completely. The problem is Starfield has issues with many other game elements (like loading screens, mediocre worldbuilding, etc). Also the fact that it was simply a game in a different genre than previous Bethesda games didn’t help. People expected a handcrafted open world a la Fallout 4 but got a kind-of-procedurally generated sandbox.

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

There is also Ladybird browser that IIRC already has a more complete web standards implementation than Servo despite being a much younger project. Though it’s still far from being ready and performance is really bad. But so far it seems that it’s going to outpace Servo.

Are they going to ethically source materials and production

Why would they do that?

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.

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.

Are you saying that not all bourgeois are the same?

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.

On PC sure, on consoles devs are always trying to lower the bar.

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.