You Shouldn't Use Manjaro
manjarno.snorlax.sh
manjarno.snorlax.sh
Figured it'd make sense to submit that article to let others know...
Unfortunately, the installer is kind of buggy. (Or was, the last time I used it.)
Then again, what installer isn't? :p
I never had any problems with the installer. Even being indecisive about partitioning doesn’t seem catastrophical.
(The Ubuntu installation that I eventually achieved didn't fare much better, btw. Meanwhile, Manjaro or Arch haven't crashed on me in years.)
I found this comment surprising. I believed this was one of those basic facts of life for over two or three decades now. I mean, look at the history of Linux distros. All of the dominant Linux distros of the time had a single trait: they made things easier for users. Mandrake Linux was the single most user-friendly Linux of its day, because installing was trivial and required little to no config to get up and running. Knoppix became hugely popular because users could just burn a CD and have a fully functional Linux distro up and running without installing anything. Ubuntu became hugely popular because it picked up Debian's solid infrastructure and gave it a user-friendly makeover.
In fact, is there any relevant Linux distro around whose killer feature was not making things easier for its target audience?
In the past there was a vocal minority of Linux users who advocated in favour of high barriers to entry and all-around user-unfriendliness, but let's not be mistaken: what they actually advocated for was ladder-pulling and gatekeeping.
I'm glad Linux has a diversity of distributions, and I trust that users are selecting distributions that provide value to them, and I'm thankful for the work that goes into the development of Manjaro.
Let the rough collaboration/competition play out.
The article touches on my main complaint: Manjaro comes with an AUR helper but does not use Arch repositories.
Think about how silly that is. One of your distros main selling point is automatic AUR access! The AUR packages depend on the official arch repos!
It’s like the worst of both worlds:
The instability of rolling release without access to the actual bleeding edge packages.
For one, it's not necessary. Most of these offshoot distributions do is install a desktop environment and put some theming on it, the package management is largely identical. Just install that stuff yourself, 99% of it is customization. Secondly don't install an OS from an organization you can't be sure is going to be around in 5 years, it's just asking for maintenance issues.
The i3 community Manjaro made me love tiling window managers. And Manjaro Architect was like a halfway point between the hand-holding installer and the minimal Arch installation experience. It helped me work out what I liked and get to the point where I could administer everything.
I wasn't aware of all the controversies. The only one that popped up on my radar was the treasurer thing. That's all too bad.
However I am looking to switch to a different distro, mainly because I've felt a strange dynamic between the Manjaro leadership and users. I would rather spend my time in a community I feel better about.
I imagine that most people don't have similar concerns, which is why Manjaro attracts users.
I'm only asking because I have a domain that also uses a certificate from Let's Encrypt / R3 / ISRG Root X1 and I've never had to renew it. (It seems like they auto-renew every 90 days?)
this is a plausible consequence of “whoa what if arch infra + polish/friendliness” turning out more popular than expected. you are no longer showing the world a proof of concept; you are now a vendor, like it or not. i'm sympathetic to the associated growing pains
that said, it reinforces my belief that past a certain point, derivative distributions are just kind of uninteresting. if you are at the level where distros primarily distinguish themselves by the out-of-the-box desktop, then fair enough. if you're down here with me in the ninth circle of hell where they primarily distinguish themselves by their package manager, the response to “ok no wait guys so like, it's debian..... but it boots into enlightenment” is just “ugh”
Arch has to have the most comprehensive documentation of all the distros. Even when I'm troubleshooting other distros I'll check the Arch wiki first!
Really though, what Linux distro has better documentation than Arch?
There does seem to be some stability issues (particularly in the boot/suspend logic/login logic), meaning that there are times where the system freaks out and will enable (for example) RAID in the bios. This gives a very disturbing recovery process, as a live-disk doesn't immediately detect that RAID is enabled and no drives are found by the bios otherwise, but the grub firmware remains in the boot-up process.
I wouldn't recommend Arch for all users, and the switch between AUR managers, packages etc is definitely some deep topics for most.
Personally I think Arch, even Majaro, is better than the Canonical path.
There is no better or worse either way. Each distro has its own target audience. Arch is good as a personal work horse, but to charge money from enterprise users, LTS releases are needed.
[1] Software and Updates is the app's name I believe.
This isn't something Manjaro adds.
While I don't know the technical side of things now, Manjaro was great as a product. It was far more stable than Ubuntu which was unstable and had older packages. Manjaro's community was awesome and they used to listen to the community as well. The forum was one of a kind. I learned a lot and made good online buds there.
Things started to change when they jumped into business and wanted to make money. They started becoming ignorant of requests and complaints from community. They also stopped doing the original way of things with respect to the distro. That is, they started violating the 2 weeks thing with packages. They sometimes for selective packages went directly to upstream devs ignoring the arch repos. KDE and Systemd are examples IIRC. This means the advantages of tested arch packages arriving to your system 2 weeks after was not there anymore. This borked a lot of systems and brought new issues issues as well. Their excuse was they wanted latest packages. But KDE was connected from a git repo if I remember it correctly. I am not sure if that was stable releases but from development branch of KDE (please verify this specific part, I might be wrong about this as I don't remember well. I don't want to be spreading fake news). Also, systemd. This meant directly going to upstream dev packaging without arch's testing or whatsoever. I remember increased borks after this started happening.
Then just like the blog post mentioned, Jonathon who was handling community and loved by the whole community was thrown out of the team because of the money problem. He was the glue between community and devs. He always tried to help the users. And once that happened, I started became very skeptical.
To make things worse, they had an issue with forums and it went offline. Instead of recovering from backup, they created a new forum where we all had to re-register. The old forum had all the conversations about the money issue which ended up with Jonathon being kicked out. And all the old users from beginning who have been there from the beginning. Their excuse was they wanted to start fresh. They did bring the old forum back in a different URL and put it in read only mode. But I always found it the most effective tactic to kill things slowly. Not bringing back the old one would be extremely criticized. They lost a huge chunk of old users who were frustrated for varied reasons then. They mostly left frustrated. And most new users wouldn't know or ever come across the old conversations. Most old users didn't join the new forum. And all the conversations was smartly hidden away this way. They can wash their hands off by saying - hey! It's available to read. We are not hiding anything. The worst was that they made the new forum bloody strict. This meant no more questioning the team. That was my tipping point. I installed arch and been happy. I saw Jonathon in Arch. Not sure whether he is working with Arch team.
They messed up a perfect system. They could just continue with the old way. Manjaro could've helped arch a lot. But they don't. They did revolutionise things like Manjaro Hardware Detection (MHWD) which automatically installs all your drivers including the graphics card in single click. You could install multiple kernel versions and switch between kernels. This was all nice at the time. But they borked it for some cash. Glad I moved on. Looks like they messed it up technically as well in the last 3+ years.
My finger wasn't very on the pulse of the Manjaro community, but my experience with the OS and with the (new) forum didn't seem diminished after the "companyfication".
I, too, have switched to Arch, 95% because I felt ready to (as someone else wrote, "Manjaro was my bridge to Arch across the chasm from Ubuntu") and wanted to try it, 5% because I'd rather trust a mysterious cabal of devs than a company with a bottom line that can get bought out or whatever.
I don't have trouble believing you though; they say $$$ is the root of all evil for a reason.
Which never happens, even on Arch, where packages aren't held back for 2 weeks like on Manjaro.
Both Arch and Manjaro have been way more stable for me than Ubuntu ever was, and I've used them for like 4 years now. It's counterintuivie, but newer packages seem to work better than older packages. My pet theory for this is that the devs spend most of their attention with the newest versions of their packages. Submit a bug for a DE, and they might tell you to install the newest version to replicate it there (yet you're on Ubuntu...).
I like getting newer packages (which work better) and DEs (which crash less -- see KDE Neon) and faster hardware support.
I'll never go back to a point release distro like Ubuntu or Debian. (Although, apparently, Fedora keeps their packages as new as my Arch system does, the last time I checked, so maybe that'd be an exception. :p)
It has happened to me, an update broke my sound card and I didn't know until I tried to use it at a time that was extremely inconvenient to me.
> Submit a bug for a DE, and they might tell you to install the newest version to replicate it there (yet you're on Ubuntu...)
Known bugs have known work arounds, I can deal with that. What I can't deal with is surprise new bugs in cutting edge software.
That can happen updating infrequently too, and can be harder to work out the cause.
Convenience-after, sure, but this whole distro is built around convenience-first and sometimes convenience-only. I mean we're also not talking about first offenses here. Ensuring you SSL key is valid is table stakes for an operating system hosting packages, but falling down four times? It's just obviously not a priority which is unsettling for a product that installs and maintains all your software.
If this was a group of devs building a digital egg timer, I'd agree with you, but this is your *operating system* we're talking about.
The only real benefit of Manjaro, as I see it, is a somewhat easier install path, but with the nascent archinstall script, that benefit is mostly gone anyway. If we're looking beyond the Arch-sphere, there's of course a healthy smattering of options with more on offer. You don't have to jump to Debian or Red Hat for quality and stewardship. Just because it's FOSS certainly doesn't mean there isn't real competition.