The downside is complexity. I don’t need to push or pull files for a 2 line change.
Usually I just open the file (in nano :)), change it, save it. Most of the time this works, when it doesn’t, I quickly undo the last change and try to figure out why it didn’t work. If I need to do a bigger edit that may not be as fast to undo or I am not sure if the change is going to work, then I either make a backup or a test copy.
But with source control I probably would have to do something like this: edit the file on one server, push the change to the git server (also writing a comment on how I added a semicolon), then pull it on the “use” server that I need. If I have two “use” servers and the files in both need to be slightly different, I get even more complexity.
And honestly, if there was a situation that my change broke something, but it became apparent a month later, I could probably debug the breaking faster (imagining it was some new bug) than I could going through change history trying to figure out if that change was the one which broke it. I either still remember the change or if I don’t, then just debugging it would be faster.
This has not happened to me. My stuff either crashes immediately, works OK or seems to work OK, but I get calls that it actually doesn’t work in about 15 minutes.
Probably the longest time I have to wait for answers is when I am tweaking a backup script. I change it, run it, but it may run for a few hours or longer.
My stuff is very simple. One of the more complicated things I did was modifying the code of Storj v2 node so it would use files for storage instead of some kind of a database (which was really slow if it got big). The complexity was because it was a language I did not know (node.js) and the code was split into multiple files. Still, do the change, fire up a test environment, try to upload a file, download a file, delete a file, it if works, update the node and replace the 2-3 files I edited. It actually worked quite good.
That’s cool, still no scrollbar to quickly go back up 1-10k lines (I don’t know from the beginning). From what I see in the screenshots, tmux is usually used to display multiple windows side by side, though I guess it probably can be used to display one window/tab at a time with some kind of title. It may be useful if I cannot easily use my GUI client to connect to that server, but. Still a GUI client has tabs, windows that can overlap (this is quite important to me) and scrollbar
I like using the mouse, I guess that I got used to it, since pretty much all the time I used a PC it was Windows and I used DOS only to play some games, but even then, Norton Commander supports mouse
I don’t know, but something not being “a thing” or being “unsupported” does not stop me from using it. There is an alternative that runs on Linux, though I do not remember what it’s called as I don’t use in on Linux. I can use bash or php there.
EDIT: GUI ssh vs CLI ssh. I use CLI ssh a lot - in scripts, connecting from one server to another. It is useful because I can do zfs send | ssh x zfs recv
. However, I do not really need that in the initial connection from my PC to the server. The most I need is to upload or download files and some ssh clients also have scp or zmodem support for that.