Why would you develop software over SSH is seriously beyond me.
I love that this straw-man argument pops up in every thread I read about editing text or IDE debate.
As someone who leverages SSH in their average work day I can explain my personal reasons. Let me be clear; this is likely not the way you work but it is how I work. I am not defending the merits of this for you but that they warrant my approval. If any debate is to be made in this it is that all users have a choice and those who prefer SSH should have every right to use it irregardless of any unemphatic assertions to the contrary.
I have a Linux desktop that has two very nice and pretty monitors. Given a choice I would wish my development to take place on that machine. However, the development I do is on a work computer that happens to be a small Mac Laptop (I don't get to choose the hardware I must develop on). Of all the different methods to edit files I found that SSH into the laptop from the Linux box to be the most efficient and eloquent solution while still keeping the work information on the work computer. I edit in Vim. I test with the browser running on the Mac. I can clearly see and manipulate the source on the pretty monitor while seeing the results on the little LCD screen.
Pairing like this is a huge win. Instead of Forcing a pair partner to wait for me to Alt-Tab the right screen they can connect via SSH (tmate.io) and on their end have their terminal on one monitor and the Zoom / screen share on the other. This way they can edit or watch and see the result without any ask to Alt-Tab. I can read the code while they look at the result. It is truly asynchronous code-pairing.
Comments
I love that this straw-man argument pops up in every thread I read about editing text or IDE debate.
As someone who leverages SSH in their average work day I can explain my personal reasons. Let me be clear; this is likely not the way you work but it is how I work. I am not defending the merits of this for you but that they warrant my approval. If any debate is to be made in this it is that all users have a choice and those who prefer SSH should have every right to use it irregardless of any unemphatic assertions to the contrary.
I have a Linux desktop that has two very nice and pretty monitors. Given a choice I would wish my development to take place on that machine. However, the development I do is on a work computer that happens to be a small Mac Laptop (I don't get to choose the hardware I must develop on). Of all the different methods to edit files I found that SSH into the laptop from the Linux box to be the most efficient and eloquent solution while still keeping the work information on the work computer. I edit in Vim. I test with the browser running on the Mac. I can clearly see and manipulate the source on the pretty monitor while seeing the results on the little LCD screen.
Pairing like this is a huge win. Instead of Forcing a pair partner to wait for me to Alt-Tab the right screen they can connect via SSH (tmate.io) and on their end have their terminal on one monitor and the Zoom / screen share on the other. This way they can edit or watch and see the result without any ask to Alt-Tab. I can read the code while they look at the result. It is truly asynchronous code-pairing.