Third thread in /t/ asking about this

>>1677 sorryyyy, I am a bit newer. I'll look at those threads

I've made the switch to Mint. Figuring mostly everything out okay. It's definitely worth it to avoid microsoft

Sanae the mlemer here, there are many technical reasons to choose one distro over the other, but when you are starting out these are not really relevant to you until you start getting nagged by them. Linux Mint is a good choice to get started, it's what I started with as well. While there are many technical differences between distros, some are not real. For example you don't need to pick a specific distro for gaming because all of them can game, it's more of a matter of wanting to pick a gaming distro for having gaming packages installed out of the box. How a system looks like is also entirely up to you and not the system, with the exception of very few systems like Linux Mint where it only officially supports 3 desktop environments

Do not install anything like ubuntu, debian, fedora, or linux mint or similar sort. These are n00b distros. Install gentoo and be elite like the rest of us.

>>1690 What if my processor is too weak to compile everything

>>1691 You can use binary packages for heavy stuff.

>>1692 What if I'm retarded?

ghostbsd

>>1676 Depends on how good you are with computers already and how much you want to learn. If you just want to use it casually and avoid most of the learning (which I dont think you should do but your call) then go with something like Mint, if you do want to learn about it then either go EndeavourOS if you want an easy start or Arch if you also want to learn how to manually install linux. Gentoo is great but I think it could be a bit overwhelming if you are used to just clicking .exe files. After a lot of Gentoo I switched to NixOS because I have many computers and Im lazy.

Mint with cinnamon. A combo that's as good as it should be delicious

>>1676 I made the switch to Mint a few months ago and very happy thus far, I would never ever go back to Windows after this. Some games actually perform better on Linux than they natively do on Windows, that's how shit Windows has become.

>>1737 the only reason I'd want to switch is honestly getting some cracked games to work and excel. i don't see a point otherwise

>>1738 Well Windows 11 openly spies on you so maybe Windows 10 does it too even if it is in a more subtle way. It's also about not getting ads and useless notifications in an OS that they actually make you pay for (haha). Main benefit of Linux is it's far less likely to get malware on your PC, there are probably a lot more upsides that I don't know about but someone more tech-savvy could name those. Install it in a VM and see if you like it.

>>1740 oh i've used arch linux since a year back i mean switching back to windows copilot and ai bubble stuff being included was a huge reason i switched

>>1692 If I end up using binary packages anyways then is there really any point to use a source based distribution?

>>1742 The point is being able to pick and choose options at compile time instead of being forced to use a binary that has a bunch of crap you don't need bundled in or options you do need not bundled in. By compiling from source you can avoid tons of dependencies or access things people claim are "deprecated". For example, many applications still support building with gtk2 just fine which allows you to avoid all the stuff wrong with modern gtk/gnome. By excluding a lot of things you can have a much faster, secure and easier to maintain system. Things like Arch Linux aren't really minimal. They're just as bloated as something like modern Ubuntu. With Gentoo in particular now there is no reason to avoid it. The vast majority of ebuilds only take a few seconds or maybe 1-2 minutes to build from source. Portage now supports binaries as well if you want them. But you don't need portage to build from source of course. Learning how to use make is very useful no matter what OS you're using. It means you can grab source code as soon as it is released and run it. Or you can grab old stuff people no longer offer builds for and run it. Building from source offers you true freedom. When you use binaries you're a consumer and forced to use whatever you're given. Most people offering binaries do not have your best interests in mind. I'll give you a good example; Lately everyone has been pushing things like wayland and pipewire hard. Both consume a ton of resources. They say you need pipewire for the pulseaudio support because a lot of things like Firefox dropped support for pure ALSA. If you build from source you get the option to build for sndio instead. A much better and stable sound server that consumes almost no resources at idle. Even when it's using resources it doesn't use hardly any. It can run on any hardware from the 1980s and newer. It has much better mixing options than Pulseaudio/pipewire. It is actually documented. It lets you do anything you want like route sound to multiple devices, over a network or do stuff like let application A use the left speaker and application B have the right speaker. It's the best sound server going. Everything has support for it but it's usually not built into binaries on most distros. So you have to build from source to get it enabled. Unless you use OpenBSD. Even FreeBSD requires building ports from source most of the time to use it. Even though Firefox supports it out of the box and it would be much better than what they're doing now (forcing user to install pulseaudio running on top of OSS their native sound server). Maintaining a system on something like Gentoo with tons of things disabled by default like dbus, polkit, pipewire, systemd etc. is not hard. Once you've configured everything it continues to just work forever. You can avoid 99% of the issues with modern Linux by changing some USE flags. Of course this is possible on any distro provided you're willing to manually set compile time options for everything. But it's easier to just use portage or a BSD+ports tree. Even with all that stuff disabled every modern application and games work. In fact, they usually work better. Which proves that this crap being a requirement is a huge lie.

>>1745 Also concerning Gentoo: It becomes much easier to maintain multiple systems after you've initially configured USE flags. There is nothing requiring you to build from source on a really old slow machine or use someone else's binaries. Most people using Gentoo end up setting up a local build server. Usually their fast PC or home server. Your local build server compiles packages for all your machines. Then those machines (your laptop, your TV set-top device, your old 1998 600Mhz Intel CPU PC, your little ARM system on a chip) can all fetch packages from your local server. Keeping them up to date usually much faster than they would using some mainstream distro that relies on someone else building the packages. You can even build generic packages that work everywhere or have them optimized for each and every system based on their CPU flags. You're building your own distro in other words. Which is why Gentoo is called a "meta distro" by some people. Now the Gentoo project isn't perfect. It has been taken over like most everything else. But thanks to Portage's USE flags you don't have to follow what mainstream Gentoo repos ship by default. Gentoo has a user repo called GURU which is basically like Arch's AUR. Except the packages are much higher quality and better tested. There are tons of pre-made overlays there if you want to do something like replace OpenRC+systemd shims/systemd with something like s6 or runit. There are overlays for doing things like pro-audio/video editing and most everything else you can think of. With Gentoo it's still possible to run a full blown desktop environment using nothing but gtk2+qt applications which are built from modern application source code. You will find that ability no where else. Any distro shipping pre-built binaries and even Gentoo's default config will force you on to gtk3/gtk4 tool kits. With Gentoo you don't even have to run something like udev. You can still run a static /dev without losing the ability to use your hardware and storage devices. The only difference from a udev system is you have to build in support for your input devices manually and manually mount things like usb thumb drives and external HDDs. Which isn't a big deal it's just running "mount". This is also much more secure than the default in every other distro. Since no one can plug-in something like a usb thumb drive into your computer and access it automatically. They can't plug-in devices like key loggers either because they will not work. The system will not mount or use anything automatically. You can also replace udev with something else like mdev if you really want that type of functionality. Impossible to get root through an exploit through systemd+polkit+PAM as well if it isn't on the system. Impossible to get it through sudo too if you don't have it installed. You can use doas instead if you really want that ability or simply use su+switching tty when root is needed. By having a unique system built from source code you avoid 99% of exploits automatically even if you don't understand the underlying code. Your configuration is so unique that no one will write an exploit for it. They'd have to manually access the system somehow then spend a lot of time crafting an exploit for it. Chicken and egg problem for them. Also there is an actual tangible gain in speed on most systems if you build for your CPU's abilities instead of using generic binary. Sometimes it isn't just speed either it's use of resources like RAM. Since if you've excluded half of the crap it claims it needs but really doesn't you don't have that shit in RAM. Nor do you have it spawning daemons and such.

gentoo is cramping my ubuntu-designated workflow. never seen anything seamlessly substitute ubuntu-based distros for the devving they're used for