Hacker News Reader

Comment by wanderingmind | Hacker News Reader

Maybe some VSCode users can tell me what specific actions Lazygit do that Gitlens (free version), can't do? And gitlens can do a lot (stash handling, commit revert, branch checkout from remote, autofetch, rebase and many more). Or is it just a different workflow that others find easy to use?

View on HN

I use VSCode but not git lens. I don't think it does much that Lens doesn't, it's indeed a different workflow for me: I don't like to use the mouse so the clicky-clicky workflow of Lens doesn't work for me, I'm much faster with lazygit (and I can instantly drop to the `git` CLI if there's something I don't know how to do with lazygit, as I'm already in the terminal).

I'm not particularly keen to have my VCS and my code editing in the same software really, although I wouldn't say that it's a superior approach.

My personal take: I like using the keyboard. Lazygit works very smoothly with the keyboard, of course.

I tried the git thing that’s part of vscode and it really wants me to click. It is theoretically possible to get by without, but it’s cumbersome.

Thanks that makes sense especially for folks that use keyboard and like to do it within CLI.

> I'm not particularly keen to have my VCS and my code editing in the same software really, although I wouldn't say that it's a superior approach.

Addendum: I'm also not always using VSCode. Sometimes I just use vim if I'm already in my terminal and it's a small edit, at which point I don't want to have to go back to VSCode (potentially having to open the project) just for git

I thought I was a weirdo for splitting my usage between VSCode and nvim. I do the same! And I don't even use any fancy vim features. I think it's a mental separation for me: "right now, I am doing sysadmin stuff and need to have my sysadmin brain on" vs "right now, I am developing software and need to have my software brain on", but I'm not even really sure about that.

My workflow is similar. For one larger project, I am just more comfortable operating in VSCode, but if I need to work in a smaller project, I tend to just fire up NeoVim, and I've found the transition to Lazygit to be fairly smooth.

Reply on news.ycombinator.com