5 ms·

I'm curious how much people prefer TUIs over editor-plugin-GUIs these days. I'm getting more and more persuaded by the plugin model personally - perhaps partly

I'm curious how much people prefer TUIs over editor-plugin-GUIs these days. I'm getting more and more persuaded by the plugin model personally - perhaps partly by how easy it is to discover, install, update, uninstall, etc VSCode plugins

hahn-kev 3y ago
Jetbrains has this down so well. I sometimes wish I could open up a light weight version of their IDE just for git management.
piuantiderp 3y ago
Emacs has had this forever...
WhereIsTheTruth 3y ago
The state of desktop application is pretty alarming, everything is its own web browser.. I'm glad people still build these TUIs, that's exactly what i need, simple interaction with my keyboard, no fuss, no bloat (edit: just checked, the executable is pretty large ~5mb, I wish Go made some effort in that area), a simple executable that can run on my headless server through SSH
ar_lan 3y ago
I prefer it, but I also prefer to stick to the terminal as much as possible. If I were a VSCode user, I might disagree. My main factor is I don't want to have to context switch across applications. I don't feel like I'm doing that if I stay in the terminal. As such, I would imagine if I were a VSCode user, I'd prefer a git plugin there. VCS is very much tied to the code, so I think it makes sense to co-locate.
heywire 3y ago
The built in support for git in Visual Studio 2022 is pretty good, but I do occasionally find myself reaching for the command line still.
benrutter 3y ago
I don't know if it's a "I want a TUI rather than a plug-in" vibe. For me, it's more of a "it fits my workflow". I use helix as an editor and like to use a range of command line tools and scripts for regular stuff. Lazygit fits right into that and I don't have to leave the terminal. I used vs-code a few years ago and its got plugin was (I assume still is) pretty good, if I used it as my editor then I'd probably use a plug in like you say, but as things are lazygit is both an awesome tool and the path of least resistance.
bilekas 3y ago
Recently for conflict resolving i will open up vs code. I find it so much more reliable and convenient there. I can quickly see the conflicts resolve then stage. But when it comes to more detailed things nothing compares to the cli. There is a small learning curve for the commands but it's minor compared to the intuitive control you get. A lot of the dedicated tools are just too bloated and use different terminology than the git standard which baffles me. My colleague will use source tree and Everytime I see him doing stuff I always think : "But that's not what the got command is called for that".

hahn-kev 3y ago

Jetbrains has this down so well. I sometimes wish I could open up a light weight version of their IDE just for git management.

piuantiderp 3y ago

Emacs has had this forever...

WhereIsTheTruth 3y ago

The state of desktop application is pretty alarming, everything is its own web browser.. I'm glad people still build these TUIs, that's exactly what i need, simple interaction with my keyboard, no fuss, no bloat (edit: just checked, the executable is pretty large ~5mb, I wish Go made some effort in that area), a simple executable that can run on my headless server through SSH

ar_lan 3y ago

I prefer it, but I also prefer to stick to the terminal as much as possible. If I were a VSCode user, I might disagree. My main factor is I don't want to have to context switch across applications. I don't feel like I'm doing that if I stay in the terminal. As such, I would imagine if I were a VSCode user, I'd prefer a git plugin there. VCS is very much tied to the code, so I think it makes sense to co-locate.

heywire 3y ago

The built in support for git in Visual Studio 2022 is pretty good, but I do occasionally find myself reaching for the command line still.

benrutter 3y ago

I don't know if it's a "I want a TUI rather than a plug-in" vibe. For me, it's more of a "it fits my workflow". I use helix as an editor and like to use a range of command line tools and scripts for regular stuff. Lazygit fits right into that and I don't have to leave the terminal. I used vs-code a few years ago and its got plugin was (I assume still is) pretty good, if I used it as my editor then I'd probably use a plug in like you say, but as things are lazygit is both an awesome tool and the path of least resistance.

bilekas 3y ago

Recently for conflict resolving i will open up vs code. I find it so much more reliable and convenient there. I can quickly see the conflicts resolve then stage. But when it comes to more detailed things nothing compares to the cli. There is a small learning curve for the commands but it's minor compared to the intuitive control you get. A lot of the dedicated tools are just too bloated and use different terminology than the git standard which baffles me. My colleague will use source tree and Everytime I see him doing stuff I always think : "But that's not what the got command is called for that".