stevedice

joined 3 months ago
[–] [email protected] 1 points 1 day ago (1 children)

Yep. That's what I'm saying, Linux isn't ready.

BTW, on my system /boot is ext4, /boot/efi is FAT32 and the rest mounted at /sysroot is BTRFS.

Your installation is probably quite old. It used to be like that but now the default is mounting the ESP to /boot. The old way makes way more sense to me, btw.

[–] [email protected] 1 points 1 day ago (3 children)

The /boot partition is FAT32 due to RedHat's stupidity but that's neither here nor there. The point is that regular users don't know how to boot into a previous version of the OS. Yes, I know you just have to select it on GRUB but a black screen with a list of kernels qualifies as broken for regular people.

[–] [email protected] 2 points 1 day ago (1 children)

Linux does do the black screen and hope you don't touch it, at least OpenSUSE and Fedora do. And that's a good thing. The "reboot to update is bad" meme needs to die but I digress. I'm skeptical that Linux is more resilient than Windows when it comes to updating but even if it is, Windows automatically rolls back failed updates while Linux will boot you into broken system and expect you to know what to do. Regular people can't deal with this, even if the answer is a simple as selecting a different entry from the GRUB.

[–] [email protected] 1 points 1 day ago (1 children)

What you stated was a lie. I don't know what to tell you 🤷🏻

[–] [email protected] 1 points 1 day ago

Even if you keep your code in a separate file, if you link to GPL code, according to the FSF, your code should be GPL. The law says otherwise but they would still sue you.

[–] [email protected] 1 points 1 day ago (8 children)

Until everything breaks because the average user held down the power button mid-update because the computer wouldn't shut down.

[–] [email protected] 1 points 2 days ago

I'm with you, I don't believe it's ready but the command line is not an issue anymore. I only ever see it because I'm an stubborn old man who insists on using Vim. Truth is, if something you do on Linux requires the command line, doing it on Windows probably requires group policy, regedit or something like that, which are equally esoteric.

[–] [email protected] 1 points 2 days ago* (last edited 2 days ago)

Not those examples!

[–] [email protected] 2 points 2 days ago

Just a couple of days ago libreoffice decided to ignore my dark application theme but still honor my dark icon theme so I had white icons on white background making it basically unusable. Took all of 30 seconds to fix but imagine it happening to my 65 year old mom.

[–] [email protected] 3 points 2 days ago

Oh, boy. Go on. Try that experiment. A regular person will encounter problems you could never imagine would be a problem in the first place. Say what you will about Windows but it at least has ~30 years of experience dealing with regular people. Switching my mom to Linux because "all she does is browse the internet anyway" is exactly how I became part of the "Linux isn't ready" crowd.

[–] [email protected] 3 points 2 days ago (12 children)

Until everything breaks because the average user hasn't bothered updating.

[–] [email protected] 7 points 2 days ago (2 children)

Nothing that requires the command line in Linux can be done in a "friendly" way in Windows.

view more: next ›