

43·
8 days agoDefinitely the command. CLI commands are simple and portable. Asking the user what DE they are using for an extra round trip and then making a description of the pointy-clicky-ceremony has way to much friction.
Definitely the command. CLI commands are simple and portable. Asking the user what DE they are using for an extra round trip and then making a description of the pointy-clicky-ceremony has way to much friction.
My dad who retires today and who has been a Windows user since roughly 1993 has set up multiple Pi-Holes and OpenVPN in the last few years and recently even installed Ubuntu in WSL so he can run bash scripts locally too. He’s not in a tech job, he’s a doctor.
A year ago my friend who has been using Windows for his gaming for the last 22 years asked my to help him set up a Fedora dual boot. Just to play around with, even though he doesn’t have a tech background. He didn’t really use it much. But today his work had him blocked by their own fuck-up and he decided to use the time to try it out again.
This evening he told me about how he upgraded his Fedora back to a current version using GUI tools. Then he saw that Windows wasn’t the default boot in his grub boot order anymore. He tried to find an app for editing grub, realised this was the kind of thing people do with CLI. So in the next two hours he learned enough CLI using a free beginners lesson he found online somewhere, until he found the
history
command, where he found the grub command we used during the original setup. He was so excited about this success!I think the CLI criticisms are way overblown, and non-programmers can use CLIs perfectly well if they want to.