To play devils advocate, I’d say that the bigger issue is that Linus ended up in the terminal to start with, when he had no idea what he was doing in there.
If Linux is to hit the masses, then a beginner friendly distro should have the convention to install apps be by GUI instead of TUI, and guides should be updated to reflect this. That GUI-based installer should see that the “Yes, do as I say” prompt was triggered and in a clear and concise way, inform the user that important packages will be removed if they continue and they should not.
Effectively just having a much better interface for the user is what I’m saying.
a beginner friendly distro should have the convention to install apps be by GUI instead of TUI, and guides should be updated to reflect this
It is a lot harder (and less helpful) in a written guide to tell someone to press a button in menu such-and-such; telling someone to open the terminal and copy paste a command is easier.
In addition (though I do not know if it applies so much to gui package managers) GUI apps also have the tendency to not have a stable interface, so a blender 2 tutorial will often not be useful for someone using blender 3, because the interface will have changed and buttons that were once in one place now are somewhere else or no longer exist. CLI programs for some reason are a lot more backwards compatible in my experience.
I think GUI apps should ideally be designed to be usable without the user knowing where something is beforehand (though that is not always possible, like in complex software handling a lot of stuff a new user may not be familiar with, when they only want to achieve a certain specific goal), making mentioning how the UI works almost superfluous in those cases.
To play devils advocate, I’d say that the bigger issue is that Linus ended up in the terminal to start with, when he had no idea what he was doing in there.
If Linux is to hit the masses, then a beginner friendly distro should have the convention to install apps be by GUI instead of TUI, and guides should be updated to reflect this. That GUI-based installer should see that the “Yes, do as I say” prompt was triggered and in a clear and concise way, inform the user that important packages will be removed if they continue and they should not.
Effectively just having a much better interface for the user is what I’m saying.
It is a lot harder (and less helpful) in a written guide to tell someone to press a button in menu such-and-such; telling someone to open the terminal and copy paste a command is easier.
In addition (though I do not know if it applies so much to gui package managers) GUI apps also have the tendency to not have a stable interface, so a blender 2 tutorial will often not be useful for someone using blender 3, because the interface will have changed and buttons that were once in one place now are somewhere else or no longer exist. CLI programs for some reason are a lot more backwards compatible in my experience.
I think GUI apps should ideally be designed to be usable without the user knowing where something is beforehand (though that is not always possible, like in complex software handling a lot of stuff a new user may not be familiar with, when they only want to achieve a certain specific goal), making mentioning how the UI works almost superfluous in those cases.