I’ve seen a lot of people who quite dislike Manjaro, and I’m not really sure why. I’m myself am not a Manjaro user, but I did use it for quite a while and enjoyed my experienced, as it felt almost ready out of the box. I’m not here to judge, just wanted to hear the opinion of the community on the matter. Thanks!

  • pinkolik@random-hero.comEnglish
    1·
    1 year ago

    I use Manjaro ARM on my Orange PI because I couldn’t get Arch ARM to work on it, while Manjaro has support of my devices out of the box. Since I installed a minimal possible version (without any DE), it doesn’t feel bloated or something. It feels like I’m using Arch but with slower updates. Overall, it’s good and I don’t notice much difference from Arch. But anyway, I haven’t tried it for a desktop station.

  • DigDoug@lemmy.worldEnglish
    0·
    1 year ago

    Manjaro was my intro to Linux, but now that I know more about it, I can’t recommend it in good conscience. Letting their SSL certs expire is something that happens (even though they could automate it), but telling their users to change their clocks so it works is a big no-no.

    Worse than that is how they manage packages from upstream. Simply freezing them for two weeks is, in my opinion, the worst of both worlds. You don’t get timely security updates, but you still end up with the issues of being on the bleeding edge - just late. It also means that if you use the AUR (which is really one of the biggest perks of Arch-based systems), it’s possible that the necessary dependencies are out of date.

    I think that if one wants “Arch with an installer” they should go with EndeavourOS, or try the archinstall script.

      • Einar@lemmy.mlEnglish
        1·
        1 year ago

        Can you expand on this? A source would be great here to properly debunk this.

        • Zamundaaa@discuss.tchncs.deEnglish
          1·
          1 year ago

          Sure. When it comes to updates, Manjaro is pretty much doing what every single other distro is doing. Updates that are buggy don’t get pushed to the stable branch until they’re fixed up, and security updates tend to get pushed through faster than feature updates. The time period that updates get held up by is not a fixed duration, it depends on the specific package and update and can be anywhere between a few days and a few weeks.

          As a concrete example, with some major Plasma updates Manjaro has waited for three or even four point releases (4 / 8 weeks) before considering it stable enough vs the newest point release of the previous major release, and following point releases after that get pushed to stable much faster.

          As another point, even Arch has a very similar process… Their policy on pushing updates is far more geared towards pushing updates quickly than towards not breaking things, but otherwise it’s pretty much the same.

          Idk about a source on this stuff though. There’s stuff like https://wiki.manjaro.org/index.php/Switching_Branches but I don’t know anything better.

          Manjaro packages start their lives in the unstable branch. Once they are a deemed stable, they are moved to the testing branch, where more tests will be realized to ensure the package is ready to be submitted to the stable branch