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?
It seems that Garuda that's mentioned in this article does that.
You Shouldn't Use Manjaro
31–40 of 58 posts
Re: You Shouldn't Use Manjaro
#32I 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.
Arch's documentation is incomplete?
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!
Re: You Shouldn't Use Manjaro
#33I gave Manjaro a try a few years back. It wasn't too bad, actually. But then an upgrade made it impossible to boot into the desktop, and there was no fix. So it was bye-bye Manjaro. Sounds like things have gone downhill with the distro. Too bad.
Re: You Shouldn't Use Manjaro
#34Earlier 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
without being disrespectful, the installer that does not fail is the red hat / centos / alma / rocky installer. btw, archlinux user here
Re: You Shouldn't Use Manjaro
#35I 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.
I’m having trouble relating to this post. General linux questions on a search engine end up on the Arch Linux wiki quite often.
Really though, what Linux distro has better documentation than Arch?
Re: You Shouldn't Use Manjaro
#36Earlier quoted context omitted.
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…
> Which never happens,
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.
Re: You Shouldn't Use Manjaro
#37Earlier quoted context omitted.
> 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…
> Which never happens, 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…
If your kernel gets updated, things that rely on kernel modules may not work properly until the system is rebooted. It's always good to delay kernel updates until you have the time to reboot.
Re: You Shouldn't Use Manjaro
#38As someone who used Manjaro for ~4 years, Manjaro used to be a perfect system. I never borked my system in all those time. It had strong defaults and it taught me well that I am using Arch for the last 3ish years without issues. I will be grateful for that I guess. 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…
It seems that Jonathon has moved over to Endeavouros which does seem from my reading to be Manjaro done right.
Re: You Shouldn't Use Manjaro
#39Is it possible to automate tar.gz files to compile and install on Unix? Or does there have to be a manual set of make files like BSD ports.
Can you elaborate a bit on what you mean? It's a bit difficult to install build artifacts directly into the system. There are problems like tracking version compatibility, installing resource files and tracking artifacts for removal etc. This is what packages and package managers do. If you wish to take that route, then Arch PKGBUILDs and Gentoo Ebuilds are reasonably easy. Ebuilds have a lot of similarity with ports. Debian's checkinstall is also somewhat successful in it. Nix and Guix also allow you to do this - but the approach is slightly different from the rest. However, all distributions need some metadata and procedure from the user/packager to achieve it.
Re: You Shouldn't Use Manjaro
#40I thought HN people love Manjaro. I installed Manjaro because it was the majority of HN recommended