Practice in a VM and see for yourself! I did that, set everything up, and ultimately decided it was more system admin detail than I wanted to take on. But as far as ease goes, it’s not especially hard, there’s just not much in the way of hand-holding or preset configs, and you’ll likely find there’s a lot of preinstalled drivers and things you take for granted.
archinstall is easy. The hard part about arch is maintaining it and keeping up to date with linux innovation. As long as you keep reading forum posts and news about linux and browse the arch wiki, there’s nothing wrong with it. If you do not ever read about advances on linux, then don’t use arch.
If you can put together Lego with the instructions or IKEA furniture, you’ll be fine. It took me three tries, and I learnt stuff from each mistake, so the worst that can happen is you learn.
I think that a lot of the recent GNOME design choices are merely because they’re trying to improve usability on mobile devices. It also just so happens that Apple is trying to make the macOS desktop closer to iOS to encourage people to move from Windows. They have similar goals, which leads to similar design choices. And all design is derivative, anyway. Who cares.
You aren’t wrong, but that has nothing to do with he issue at hand. They should copy each other if a solution is good, and that’s the issue here, GNOME forgot to copy a good UX practice that Apple actually took the time to implement.
Because Fedora is open source only to the point of it being pathological. If there isn’t am open source driver most time you’re just boned. Someone new is going to have a tough time with it, and the community is on average a very “lol rtfm” bunch. Not as bad as Arch, but that’s not saying much.
Meanwhile, despite the problems around Ubuntu, Debian communities are much more understanding and helpful. Mint even with old packages is going to be an easier time for a newbie. Certainly a newbie unfamiliar with the way entirely too much of the FOSS community is.
To be fair arch has amazing docs, and even a rube like me can follow it decently well. I found endeavor to be the easiest distro to use. But agreed the attitude isn’t great.
Arch is absolutely divine with its documentation. There is a bit of a “you must be this tall to ride” with them though. Like the tiny [AUR] link. That’s not really well explained, and is even more opaque if you follow the link.
As a very long time Arch user I wouldn’t say “easy” like everyone else seems to. I absolutely would not suggest it for a first distro for someone, which is what I would classify as the “easy” level.
But if you’re comfortable with using Linux, the terminal, and being able to follow written documentation you’ll be able to do it just fine maybe with a little frustration the first time. If you’re installing to a laptop, make sure to look up your model on the wiki first.
I’ve been using bazzite for over 6 months now, I have it on three of my devices at the current moment in time, and I would never look back to Windows at this point, shit just works.
I have three questions if you have the time. Can you make it go to desktop mode by default, not big picture mode? What DE does it come with, Plasma? Does it come with Lutris or whatever? If I have an .exe installer for an old game, does it come pre-installed with tools to help create the proton wine-prefixes and everything? I imagine the last one would allow Flatpak to be used.
I apologize for the late reply, the other commenter is correct as well, Bazzite comes out of the box in desktop mode, if you’ve ever used plasma before, it’s a lot like that. For .exe programs I use wine, and haven’t had that let me down yet for the most part. Im fairly certain Bazzite does use flatpaks, but it does also have also Discover baked in.
Honestly, I compare it strongly to using the steam deck desktop mode.
I want to add to what the others said. Usually I just add windows programs/games to steam as none steam game. that has been the easiest way to do it for me. I have very few games that isn’t on steam so it is nice to be able to add them together with the rest with the correct categories and such.
The reason to follow the archwiki install instructions is because it teaches you how to do a lot more than just install the OS. This will help you a lot down the line and not just with arch.
I did it few times between 2008 and 2010 when I was way younger. Idk how I did it, but after two times I was used to it and learned also a lot. Today I don’t have the nerves to install arch without archinstall or anarchy. The wiki helped me a lot. The wiki gives an excellent guide to install arch and to set up everything you need. It is well written enough, that no deep Linux knowledge is needed
The archlinux wiki is great for everything. I used it when I had Fedora, Debian or sometimes if I used OpenBSD.
In general, I would say it’s not hard, but it’s not easy.
When I did it, I had some moderate Linux experience but I was by no means an expert. I did a few practice runs on a VM and made myself a runbook before I completed the install on my real computer. This allowed me to get a real sense for what I was doing and what each step did, exactly. When I ran into differences on my actual computer, the time I spent researching and doing it on the VM helped me to overcome any confusion and complete the install successfully. The wiki has all the information you need.
So, from beginning to end, I spent a weekend on it, including the few dry runs I did on the VM and configuring my system after the actual install was complete. If you’re not already quite familiar with Linux, I think it’s wise to do it this way because you build in time to learn, as opposed to just getting a working system as quickly as possible.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.