Part of the reason for a command line is being able to reproduce commands exactly. Going back through the command history is an important part of that.
A GUI with good usability can let you repeat commands exactly if required. They use last used values as default. If people in needed that often we’d see more of it in GUI apps. There is often more useful functionality that get prioritised though.
It is done, but it comes in specifically packaged form for each use case.
Postman is essentially a GUI app for reproducible curl commands. There’s nothing in Postman that couldn’t be done by a good shell script, and it will spurt out a curl command if you want. To get this in a shell environment, you need to have the knowledge to put together tools that are sitting right there. To get it in a GUI environment, you need a team of people who probably know how to do it in a CLI, but then create a complex memory hog GUI to do it otherwise. None of that development effort is directly transferable to any other problem space.
That’s not necessarily so. There are all sorts of legacy reasons people give for making poor software. From lazy monopolies to programmers with little understanding of usability. To people without the big picture. It will change.
Sadly, big business, techies without imagination and community FOSS without enough capacity are the ones that control what is available. Nothing will suddenly change. Usability is way down the priority list.
Part of the reason for a command line is being able to reproduce commands exactly. Going back through the command history is an important part of that.
A GUI with good usability can let you repeat commands exactly if required. They use last used values as default. If people in needed that often we’d see more of it in GUI apps. There is often more useful functionality that get prioritised though.
It is done, but it comes in specifically packaged form for each use case.
Postman is essentially a GUI app for reproducible curl commands. There’s nothing in Postman that couldn’t be done by a good shell script, and it will spurt out a curl command if you want. To get this in a shell environment, you need to have the knowledge to put together tools that are sitting right there. To get it in a GUI environment, you need a team of people who probably know how to do it in a CLI, but then create a complex memory hog GUI to do it otherwise. None of that development effort is directly transferable to any other problem space.
That’s not necessarily so. There are all sorts of legacy reasons people give for making poor software. From lazy monopolies to programmers with little understanding of usability. To people without the big picture. It will change.
Why would it suddenly change now, decades after the first GUI operating systems were available to average people?
Sadly, big business, techies without imagination and community FOSS without enough capacity are the ones that control what is available. Nothing will suddenly change. Usability is way down the priority list.