Live data from Hacker News

You Shouldn't Use Manjaro

manjarno.snorlax.sh

21–30 of 58 posts

Re: You Shouldn't Use Manjaro

#21
arch itself had a similar reputation for half-assing security etc; package signing was a big sticking point back in the day

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”

Re: You Shouldn't Use Manjaro

#22

I use manjaro as a daily driver. At the time I switched to the distro it was perhaps the only accessible Arch distro and was highly recommended. 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 im…

Enterprises have different priorities from individual users who use Linux as a "daily driver". The last thing they would like to see is an upgrade disrupting their production, and many of them postpone upgrades unless required to. Enterprise Linux are expected to be predicable and companies like version numbers and golden images, and obviously a rolling release is not good at this. In short, Linux used by enterprises are treated as cattle that require minimum attention, but rolling release distros are like pets, which certainly are more delicate and fancy but at the same time require a lot more effort to care for.

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.

Re: You Shouldn't Use Manjaro

#23
post #14

I have a theory that the only reason Manjaro is popular is that for the longest time, Arch did not have an installer. Do not underestimate the power of making things easier for your users.

Arch does have an installer? :)

https://github.com/archlinux/archinstall

Unfortunately, the installer is kind of buggy. (Or was, the last time I used it.)

Then again, what installer isn't? :p

Re: You Shouldn't Use Manjaro

#25
post #13

Last time I installed it Manjaro’s value proposition was an easy path to getting Nvidia’s nonfree drivers working without hours of fussing about. Does some other distro fit that need?

Ubuntu has been packaging the binary Nvidia non free drivers for quite a few years now. There's an easy to use GUI app [1] to enable the non-free drivers, and switch between the different Nvidia driver versions.

[1] Software and Updates is the app's name I believe.

Re: You Shouldn't Use Manjaro

#26
post #14

Earlier quoted context omitted.

Arch does have an installer? :)

https://github.com/archlinux/archinstall Unfortunately, the installer is kind of buggy. (Or was, the last time I used it.) Then again, what installer isn't? :p

Ubuntu’s?

I never had any problems with the installer. Even being indecisive about partitioning doesn’t seem catastrophical.

Re: You Shouldn't Use Manjaro

#27
post #10

As an Ubuntu/Debian usooor, Manjaro has never been something that interested me. Endeavour on the other hand...

I like the polish of manjaro, I just prefer the stability of debian. Polish doesn't mean much when a rolling release breaks your computer.

>when a rolling release breaks your computer

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)

Re: You Shouldn't Use Manjaro

#28
post #26

Earlier quoted context omitted.

https://github.com/archlinux/archinstall Unfortunately, the installer is kind of buggy. (Or was, the last time I used it.) Then again, what installer isn't? :p

Ubuntu’s? I never had any problems with the installer. Even being indecisive about partitioning doesn’t seem catastrophical.

My anecdata disagrees. I've had the Ubuntu installer crash around 2 years ago.

(The Ubuntu installation that I eventually achieved didn't fare much better, btw. Meanwhile, Manjaro or Arch haven't crashed on me in years.)

Re: You Shouldn't Use Manjaro

#29
I struggled quite a bit with Arch. I found the documentation quite confusing and it seemed incomplete, and getting support was quite difficult. Manjaro provided a very easy way to try Arch. If the process to install Arch had been easier, I wouldn't have bothered even looking for any derivatives of it.

Re: You Shouldn't Use Manjaro

#30
Full agree.

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.

Post reply on HN