laughingtnt

Well, Luke is, Linus (according to himself) doesn't really play anymore, since he is pretty strapped for time.
Wow, that is a harsh statement, and I feel there might be a few things problemetic with this statement. 1: you imply that mining adventure made people buy gaming hardware, but if anything, I think it might have discouraged people from doing so. 2: kind of by definition mining adventure mostly informed "the community", so if priced rose because of that video series it did so only by selling more stuff to parts of "the community". Whether or not this can even be considered "bad" greatly depends on your idea of ethics.
Well, this meta stuff is usually touched upon on WAN exclusively, so if you want to see their side of things you should look into the episode of the week after the video you disagreed with hit YT

Oh, I still use GRUB2 for my Linux installs - both actually uses its own GRUB2!
 
Basically my setup is Clover being the 'main' bootloader so after POST it boots to Clover giving me a selection of the 4 OSes. I then choose an OS and let the OS' bootloader take over and boot that OS. So let's say with Ubuntu it goes from Clover > Ubuntu's GRUB2 with Ubuntu entries > boot to Ubuntu. Yeah, it's two chained bootloaders doing it this way (except with Mac, since Clover is its bootloader), but I don't have to mess with editing stuff except with Clover.
 
But... I can override that and boot any OS with its own bootloader if I want to during POST. Or I can boot into the UEFI BIOS and change the UEFI boot order if I need to boot another OS (but it's easier to press F11 during POST and choose a bootloader).

In simple terms the two OSes bootloaders clash and override each other.
 
I have 4 OSes (all UEFI) on this PC (Windows 10, macOS, Arch Linux and Ubuntu) each installed on its own SSD. How do I keep their bootloaders from clashing with each other? When I install or reinstall OSes I simply unplug all of the SSDs/HDDs (except the SSD I'm installing to) so they can't override each other's bootloaders during installation. Then I use a "main" bootloader to boot all of the other OS' bootloaders (Clover, in this case). Works pretty good.

That's not true must well nag yo u once a week you need to update.
 
Though most updates don't require a restart a simple log out and back in is enough. 
 
Guess that's better than Windows that goes "hey I'm restarting your computer soon"