Hi all, thanks in advance for indulging a complete newbie! I'd like to try Linux on an 11-year-old MacBook Pro (gifted by a relative), but I don't know where to start. What distribution would you recommend based on my background?
-Coming from the Mac world; haven't used a PC/Windows since before the pandemic. I'd prefer something that feels similar to MacOS.
-Not a techie. I've forgotten everything (everything!) I ever learned about command line because I never ended up needing to use it, and I haven't had to debug anything in a long time.
-What I'll be using it for: accessing the internet, various kinds of creative projects that I'll probably try making with FOSS software (something I've only recently started to look into), and making another attempt at learning programming (my interest will probably peter out before I get anywhere with it, though, because that's what happened the last two times). Probably won't be gaming. I'd prefer having the option to use mainstream office software in case anything happens to my current computer, but I don't actually expect anything to happen to it in the next few years, so that's just a nice-to-have.
-Priorities: works on old Mac hardware, good for privacy, decent software availability, not buggy, ability to avoid generative AI (i.e., no repeat of Apple installing the Image Playground app on my computer along with a software update, without the ability to remove it.)
It seems like a lot of people recommend Ubuntu or Linux Mint to beginners, but I'm seeing some people complaining that Ubuntu is has spyware(?) and forces things users don't want, and it seems like Linux Mint is usually recommended to people coming from Windows, so IDK if either of those make sense for me. Advice/recommendations appreciated!
x86 is the instruction set, 64 is for 64-bit extension of that instruction set. It's also known as AMD64 to make it even more confusing. All Intel Core processors starting from Core 2 are using that architecture, as far as I remember.
By "tinkering a bit" I meant sometimes digging up a package in the archives and rolling it back. I used Arch daily for around 2 years and had to do it once. You can also avoid it by keeping tabs on what the community says, broken packages cause quite a bit of fuss.
Release schedule is a trade off, if you are updating weekly, it'll usually take less than 5 minutes to download all the packages that got updated within that week. The rarer you update, the more time each update takes.
But it's all ultimately a matter of preference, just wing something up and try to use it for a couple of days. If it's not to your taste, scrap it and try something else, it's rare to end up with a setup you like right from the get go.
If it's just rolling back a package once in two years, that doesn't sound so bad. I don't see myself downloading updates once a week, though. I'd rather have fewer updates, especially if they're well-tested and I can set things up so they happen overnight while I'm sleeping.
I really like knowing that I won't be stuck with whatever setup I start with. Thank you!