the issue with the terminal is that you can easily fuck up really badly if you don’t know what you’re doing.
the following look the same to a new user:
rcifconfig -r0 -f puny -l all
rctrl -rall -i root -f
(both are imaginary made-up comments sothat you cannot just say "oh well obviously one does this and the other one does that)
then one goes on to nuke your home directory while the other one restarts the wifi adapter.
(and this can actually happen in practice. consider all the “always remove the french language pack” jokes that has been going around for years.)
for graphical user interfaces, you typically have icons to help you give a sense of what it’s doing, typically warning signs before you do anything dangerous, etc.
I’ve heard the jokes about rm -rf /. I’ve never met anybody who’s taken it seriously and nuked their system.
That command is legendary. It’s one of the first bits of computer lore I ever learned, about 10 years before I ever touched Linux. In fact, at that time I knew two things about Linux: it’s a free OS and don’t do rm -rf /.
Of course you should do some research first, so that you’re sure that you know what a command does, but if you’re getting it from a forum like Stack Overflow or even reddit, you can be reasonably sure that if the commenter was trying to destroy your computer they’d get downvoted and one of the other commenters would warn you about it. Don’t treat Linux like it’s some kind of minefield that you have to tiptoe around. It isn’t conducive to learning.
I think the real issue with the modern terminal, and Linux in general, is that we are using tools designed for programmers and system admins, who are expected to know exactly what they are doing, to build and run servers and treating them like they are end user tools. My grandmother was perfectly happy using a terminal for the only computer she owned because the tools it provided were simple and had those built in protections in a way that bash never will be.
the issue with the terminal is that you can easily fuck up really badly if you don’t know what you’re doing.
the following look the same to a new user:
rcifconfig -r 0 -f puny -l allrctrl -r all -i root -f(both are imaginary made-up comments sothat you cannot just say "oh well obviously one does this and the other one does that)
then one goes on to nuke your home directory while the other one restarts the wifi adapter.
(and this can actually happen in practice. consider all the “always remove the french language pack” jokes that has been going around for years.)
for graphical user interfaces, you typically have icons to help you give a sense of what it’s doing, typically warning signs before you do anything dangerous, etc.
I’ve heard the jokes about
rm -rf /. I’ve never met anybody who’s taken it seriously and nuked their system.That command is legendary. It’s one of the first bits of computer lore I ever learned, about 10 years before I ever touched Linux. In fact, at that time I knew two things about Linux: it’s a free OS and don’t do
rm -rf /.Of course you should do some research first, so that you’re sure that you know what a command does, but if you’re getting it from a forum like Stack Overflow or even reddit, you can be reasonably sure that if the commenter was trying to destroy your computer they’d get downvoted and one of the other commenters would warn you about it. Don’t treat Linux like it’s some kind of minefield that you have to tiptoe around. It isn’t conducive to learning.
I think the real issue with the modern terminal, and Linux in general, is that we are using tools designed for programmers and system admins, who are expected to know exactly what they are doing, to build and run servers and treating them like they are end user tools. My grandmother was perfectly happy using a terminal for the only computer she owned because the tools it provided were simple and had those built in protections in a way that bash never will be.