• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: January 19th, 2024

help-circle


  • Independent browser engine developers have a say in how web standards evolve. their influence is limited of course, but they use it to keep web open. Google have long been trying to integrate more “advanced” advertisement and data collection technologies directly in web browsers (including imposing it on non-Chromium browser through “open” web standards).

    The moment Google has full control of technologies involved they will do everything in their power to make ad blockers technically impossible (or at least extremely complicated and inefficient) and data collection mandatory, integrated directly in Chromium. And they will do so in such a way that most websites will simply not work on Chromium forks with these “features” disabled, so everyone will be forced to comply.



  • deadcream@sopuli.xyztoLinux@lemmy.ml"SO proof" distro
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    18 days ago

    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)



  • 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.







  • 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).