Having them remote also saves you from the window-update-hell, which annoys me no end. You can save the session and log out.
As I said in another post, I was a heavy tmux user until I started using Fluxbox. But tmux definitely had advantages. Now in the WFH world it's a good opportunity to try to optimize the workflow again.
> Having them remote also saves you from the window-update-hell, which annoys me no end. You can save the session and log out.
Yeah, I mean there's nothing stopping you from throwing up a $5 / month DO server and having your code and dev environment all configured there and then just connect to that from anywhere. As long as your network latency is low it should be quite doable.
Personally I'm ok with keeping things local because I have a single workstation where I do most of my work but I can see how a fully remote set up could be beneficial for some folks.
Absolutely, it's invaluable for just this feature. Also for digital nomad type workers who often have inferior internet to work with, and for being at the same exact spot when you left the office and get home to wrap up that last bit of work. Just reattach session and keep going. I also like to keep a freenode pane open that stays relatively uninterrupted.
As I said in another post, I was a heavy tmux user until I started using Fluxbox. But tmux definitely had advantages. Now in the WFH world it's a good opportunity to try to optimize the workflow again.