As someone who's used vim + a shell as my IDE since the start of my time using computers, it's been really awesome (and occasional eye-roll inducing...) watching people discover all these tools now that claude code is sending them into the terminal.<p>A lot of posts like this are making it to the front page of HN now that new people are exploring this world for the first time. That's great, the more the merrier, but gets a bit frustrating when a post title is written as if it's discovered some new awesome development tool or methodology, and it's just something people have been doing for years or even decades. This post isn't that big of an offender, but I'm thinking more of stuff like this [0] that it reminded me of.<p>I should try to be less grumpy about it, but I hope people also try to recognize how often these "new" tools they've been discovering have been routinely used long before LLMs. Maybe I'm just hitting my get-off-my-lawn stage, but it's a bit jarring to come to hacker news and see upvoted posts that are just "look, I can color the diffs in my terminal!". I'm glad this person discovered it, but I thought that was table stakes for the community here.<p>[0] <a href="https://x.com/dani_avila7/article/2023151176758268349" rel="nofollow">https://x.com/dani_avila7/article/2023151176758268349</a>
Having used both terminal and GUI based development environments, the good GUI environments blow terminal based workflows out of the water.<p>There are pros and cons to each. Vim can do some neat things, but GUI based IDEs are generally useful and easier to use out of the box for development.<p>The terminal tools are getting popular because people don’t need to do development. Claude is doing the development task. People just need to quickly review code in terminal.
> but GUI based IDEs are generally useful and easier to use out of the box for development.<p>This is true, they are much better for discovery and affordance, but as you progress with your tooling and tool usage there is a much higher ceiling on your productivity with other tools and their composability. In my opinion, not putting effort into learning tools ultimately holds a lot of people back from their potential.
I use both and mostly agree, but for me I don’t think the ROI for learning terminal based tooling is there.<p>They make some parts of text manipulation faster, but those parts of text manipulation take up less than 1% of my time spent working.<p>Things like debugging, which take up a large portion of my time, are not so nice in terminal based environments
Why would you say GUI based workflows are better (ignoring LLMs for now)? I would maybe give you debugging with breakpoints but for anything else I love my neovim with tmux setup
I spend more time reading and debugging code than writing it.<p>Vim and other terminal tools make doing complex text manipulation easy, but I rarely need to do anything complex when writing code.<p>I also work from different machines and ephemeral vms regularly and don’t want to spend time setting things up each time.<p>I can install vscode and the one lsp plugin I need in under a minute. In contrast, Vim doesn’t even have line number enabled by default.
Lol terminal is better for everything except maybe the one case you mentioned: first time use feature discovery, and that's debatable
That seems a little harsh. GUI tools can give us a more vibrant and useful interface.<p>But, I think the main problem is that although there have been many attempts we have not gotten to a standard way to compose different GUI tools easily or repeat actions.
I spend half or more of my time debugging and I think I would quit if I were forced to only use terminal based tools.
I completely disagree. Terminal workflows are superior in a number of ways. Most important to me are that they are more composable and more customizable. The learning curve is tougher, but the "skill ceiling" on them is higher. The ease and speed with which somebody comfortable in their terminal based environment will navigate through the tasks they need to do will always exceed what is even possible in a GUI.<p>I would say that GUIs are superior for a few specific use cases, but otherwise sub par. Step through debugging comes to mind as a good GUI use case, but even that I'm not sure if it's because a GUI is inherently better, or making a terminal based debugger is harder and so nobody has made a good one yet.
> Terminal workflows are superior in a number of ways<p>What specific ways do you find boost your productivity the most?<p>For me, the things terminal workflows can do faster take up almost a negligible amount of my workday.<p>Curious to hear if I’m missing out on a terminal workflow, or if my workday is just very different from yours