noahdvs

Every Linux distro. Just get a DE and a theme you like.

Yes, it's safer than writing down your passwords or trying to remember them yourself. It allows you to use unique, long, randomly generated passwords for every account without having to remember any of them. Doing that greatly improves your security and keeps hackers from getting into other accounts even if they do get access to one of your accounts. I personally use KeePass though.

I know and that's good. I wasn't telling you to use IceWM, just telling @EPENEX that i3wm is not a good thing to recommend here. You seem like someone who just wants something light and simple with no hassles. i3wm is a highly configurable tiling window manager, so it would be quite different from what you're used to.

it's just like a vegan trying to switch to a regular diet, you feel everything that made you special and belonging to what you consider a social elite go away. It can be really painful, especially if you had low self esteem before and behave irrationnally and a mac was somehow part of the solution to your esteem problem because you could say you had a mac and feel so proud.
 
if you was'nt brainwashed, then it's not hard at all, it's actually a relief.

LXDE, LXQt and Xfce are the 3 lightest Linux desktop environements.
A desktop environment (DE) is just the GUI that makes your OS intuitive. Without it, you'd just have the command-line, like MS-DOS.
 
LXDE and LXQt are the lightest of the 3, but are a bit more bare bones than Xfce. That's never been a problem in my experience, but I guess if you wanted to do something uncommon like use a Wacom tablet it might.
LXQt is the newest and nicest looking one of the 3.
Xfce has been around since 1996 and is the most mature, but it doesn't look like it's from the 90s.
 
Lubuntu uses LXDE, but will switch to LXQt at some point because that's where development has moved to.
Xubuntu uses Xfce.
 
Ubuntu based distros are often recommended to beginners because it's popular and there's tons of community support. Most information that doesn't have anything to do with a specific desktop environment will apply to all Ubuntu based distros.

Specs for headphones is a tricky subject, but the impedance (Ohms) is something to watch out for. Headphones with a lot of impedance will need a headphone amplifier. Headphones with a lot of impedance also tend to sound better, but you may not want to pay for or carry an amp around. Personally, I'd base my choice on headphone reviews and pay special attention to anything about durability. Nothing sucks more than paying good money for something only to see it break before you feel ready to replace it. I'd also look at the frequency responses of headphones. Flatter frequency responses are more balanced. Headphone.com is a good resource.
 
Here's the Headphone.com page for the M50x: https://www.headphone.com/products/audio-technica-ath-m50x
If you click on the "Headroom Labs" tab, you can see the frequency response. You'll see that the M50x is a bit stronger in the bass and weaker in the highs.

For the games tested, benches show no difference. For games that utilize a VM for DRM implementation, RIP. (looks at Ubisoft).

There's lots of different types of noise, so it's easy to recommend the wrong type of thing. However, you can remove noise with Audacity if you know how to use the effects properly. Actually good "magic" tools tend to cost a lot of money and are meant to be used in Digital Audio Workstations that also tend to cost a decent amount of money.

SteamOS is Linux.
 
I don't know anything about the PS4, but the thing about MacOS software being more optimized isn't really true. I don't know about Windows, but it's not in any way more significantly optimized than software on Linux. In fact, you can do more software optimization on Linux than MacOS if you use a distro like Gentoo, but there really isn't much of a speed difference at that point. The way most Linux distros compile their software packages is enough.
 
Sorry, but this tells me you don't know much about how software is made and that you haven't actually used that much software. The truth is, the developer of the app determines the app's stability way more than the developer of the OS. There is plenty of crashy software, even crashy professional software, for every OS. Even with all that, what's buggy for one person may not be buggy for someone else or their workflow many not reveal the bugs.
 
That's all I have time to respond to for now.

CSGO? Probably not. CSGO doesn't have the same ecosystem of server plugins as older multiplayer Valve games like TF2. Maybe log the commands he sends to the server (you might need to make a dedicated server if you aren't already using one) and call him out on his shit, then refuse to play with him? After you do that, he'll probably refuse to play on any server you host. He sounds like a PITA to be honest. I don't know whether you're in or past grade school and I'm not an expert, but unless he has some truly redeeming quality, I'd ditch him. I'd do whatever it takes to make him not want to talk to me again. It's a lot easier to do that kind of thing after grade school though. If he's otherwise a good person to be around, just play different games with him. You'll have to put your foot down harder than him at some point or you'll be taken advantage of whenever he feels like it.

TBH, nothing is really like Android except for Android-x86 and Remix OS, which are literally Android. Ubuntu 17.10 (uses GNOME with custom Dash to Dock extension) probably has the closest mainstream out-of-the-box experience right now. You could probably get closer with some customization if you use KDE instead of GNOME.
 
Don't do partitioning for Linux with the Windows Disk Manager. The installers that Linux distros use are much better and automatically choose settings that will work for most people. If you already have Windows installed, the automatic configuration will choose a configuration that is good for dual booting. You can also do manual partitioning from the Linux installers if you need to.

Only 3 are pinned: KeepassXC, Dolphin file manager and Firefox. I usually only have 3-7 programs open at a time.

Foobar2000 has a good frontend for conversion. It's a great music player too.

Foobar2000 has a good frontend for conversion. It's a great music player too.

In my experience, it's actually easier to do pixel art in Inkscape once you get used to working with vector graphics. Your tools in Inkscape are much more flexible. You can export sharp images at any size and you can stretch or transform vector graphics however you like. In Inkscape, if you go to Preferences->Interface->Grids you can set the grid settings so that it feels like working with pixels without having to painstakingly place or erase each pixel like in GIMP. Just use SHIFT+3 to enable the grid.
 

Oh that's easy.  PC, Ford, Android
 
Happy to help. 

Whatever you decide to do, this should help at some point, no matter the distro you use: https://linuxjourney.com/
You don't need to use the command-line to use Linux, but Linux comes with powerful tools that are worth learning and they can be faster than using a GUI for some tasks, even with just a little bit of experience.

Oh my god kid. It is filtering the blue light out by not outputting it. Just because you aren't wearing gunnars or have a sheet in front on your monitor doesn't mean it isn't being filtered

Since this thread is back, I'd like to post some more recent stats on memory usage that should give a clearer picture on how heavy various distros and DEs actually are:
 
Linux distros RAM consumption comparison (updated, 20 distros - flavours compared)   As you can see, when you have a distribution that's pretty minimal by default such as Debian, RAM usage is almost the same across DEs. Even when comparing Xubuntu to Kubuntu, the difference is less than 100MB.   The stats do not contain anything about CPU or GPU usage though, so if you know your CPU is very weak, you should probably still go for a lightweight DE. If you have a decent CPU made in the last 5-7 years, you should be able to use KDE, GNOME, Cinnamon, Budgie or Pantheon just fine.

Hmm... this Arch Wiki page says:
You seem to already have the xf86-video-fbdev package installed, so perhaps you should install the xf86-video-fbturbo-git package. It's probably a package on the AUR. If it's not available in the AUR or the official repositories, you can build it from source.
GitHub page: https://github.com/ssvb/xf86-video-fbturbo
Installation: https://github.com/ssvb/xf86-video-fbturbo/wiki/Installation
Those installation instructions are Debian/Raspbian oriented, but adapting them for Arch should just be a matter of finding the equivalent Arch blackages to install.

Also, you don't actually need to defrag on Linux if you use Linux file systems. Linux file systems like ext4 automatically organize themselves as they go. The file system Windows uses (NTFS) is what needs to be defragged every so often. Only problem is Windows doesn't read Linux file systems natively, so you pretty much have to use NTFS on your external hard drives if you want to use them with Windows and Linux.

I don't agree with everything this guy says and it's always good to be skeptical of things with "X things" titles. Videos with that format tend to lack nuance, though it can be argued that things need to be simplified for this video's intended audience.
 
While it's true that getting a computer that is known to be supported well by Linux will give you a smooth experience, you should expect Linux to work with common hardware. If it doesn't, that's a legitimate problem that needs to be fixed.
 
About graphics: Old AMD graphics cards that aren't supported by the AMDGPU driver will probably suck. Newer AMD cards should be OK. Nvidia is good for 3D graphics, but doesn't support Wayland very well and you may also experience screen tearing. I agree about Intel. If you just want your DE to look smooth and you don't do any stuff that makes heavy use of 3D graphics, use Intel.
 
I don't have strong problems with the advice about distros, except I wouldn't put Ubuntu in a separate category from Ubuntu MATE,
 
Backups are always a good idea, but dual booting is not dangerous if you use a simple installer to do the job of installation.
 
My biggest problem with this guide is that it essentially discourages getting your hands dirty, but then says the opposite at the end of this very long video. You should be aware of what will be more difficult, what will require extra work, but you should not be discouraged from exploring. Choose your own pace and chase whatever piques your interest. If you just want to do basic things and just want them to work, it's OK if you don't want to get your hands dirty. Compiling from source is no more dangerous than installing a 3rd party binary package. It's usually just a matter of installing the right dev packages and doing `./configure` or `mkdir build && cd build && cmake ..` in the directory of the extracted source code, then `make` and finally `sudo make install`.
 
 

Also, you don't actually need to defrag on Linux if you use Linux file systems. Linux file systems like ext4 automatically organize themselves as they go. The file system Windows uses (NTFS) is what needs to be defragged every so often. Only problem is Windows doesn't read Linux file systems natively, so you pretty much have to use NTFS on your external hard drives if you want to use them with Windows and Linux.

Also, you don't actually need to defrag on Linux if you use Linux file systems. Linux file systems like ext4 automatically organize themselves as they go. The file system Windows uses (NTFS) is what needs to be defragged every so often. Only problem is Windows doesn't read Linux file systems natively, so you pretty much have to use NTFS on your external hard drives if you want to use them with Windows and Linux.

I don't agree with everything this guy says and it's always good to be skeptical of things with "X things" titles. Videos with that format tend to lack nuance, though it can be argued that things need to be simplified for this video's intended audience.
 
While it's true that getting a computer that is known to be supported well by Linux will give you a smooth experience, you should expect Linux to work with common hardware. If it doesn't, that's a legitimate problem that needs to be fixed.
 
About graphics: Old AMD graphics cards that aren't supported by the AMDGPU driver will probably suck. Newer AMD cards should be OK. Nvidia is good for 3D graphics, but doesn't support Wayland very well and you may also experience screen tearing. I agree about Intel. If you just want your DE to look smooth and you don't do any stuff that makes heavy use of 3D graphics, use Intel.
 
I don't have strong problems with the advice about distros, except I wouldn't put Ubuntu in a separate category from Ubuntu MATE,
 
Backups are always a good idea, but dual booting is not dangerous if you use a simple installer to do the job of installation.
 
My biggest problem with this guide is that it essentially discourages getting your hands dirty, but then says the opposite at the end of this very long video. You should be aware of what will be more difficult, what will require extra work, but you should not be discouraged from exploring. Choose your own pace and chase whatever piques your interest. If you just want to do basic things and just want them to work, it's OK if you don't want to get your hands dirty. Compiling from source is no more dangerous than installing a 3rd party binary package. It's usually just a matter of installing the right dev packages and doing `./configure` or `mkdir build && cd build && cmake ..` in the directory of the extracted source code, then `make` and finally `sudo make install`.