|
|
|
|
|
by mixmax
4963 days ago
|
|
You make some good points, let me try to answer. First, I'm certainly not dismissing it. Yes, I'm frustrated, but I'm also aware that a lot of people much smarter than me swear by this tool, so there's obviously a lot of value there. I'm more dismayed by the learning curve. I come from a sales/marketing/ux/business kind of background so my mindset is different. I like my tools to be beautiful and intuitive. As simple as possible but no simpler as Einstein famously said. The problem, as I see it, is that the commandline is like a marathon you have to run before you reap any rewards. Learning the commandline involves a whole sleuth of different things. Finding the right tools (I can infer from your post I obviously don't have those :-)), learning how filesystems work, unixy commands, git, cygwin, the list goes on. Seen from my perspective (and this might well be wrong) you basically have to have a good grasp of a whole boatload of ideas, technologies and concepts before a commandline tool is of any use to you. There's no easy way to learn a bit at a time. It's an either/or kind of deal. I don't see any easy solutions to this, but I think it's a problem. |
|
I slowly accumulate knowledge of how to use other programs as I needed to use them (the same way I learn how to use gui programs.) The only conceptual block for me with the command-line was the concept of piping the output of one command into another.