[stragies]

How about the memory usage?

Can you (easily) nest 3mux like tmux with (auto-)grouped sessions to produce a (max) 9x9 "grid" of windows to organize your remote hosts, and their windows into an easily accessible structure. (I use this to be able to reach any window in any other terminal window on any host with max 4 keypresses)

Why choose Go? Just curious.

[aaronjanse]

> How about the memory usage?

The biggest thing stored by 3mux should be the state of the terminal screen, so memory usage should be negligible.

> Can you (easily) nest 3mux like tmux with (auto-)grouped sessions to produce a (max) 9x9 "grid" of windows to organize your remote hosts, and their windows into an easily accessible structure. (I use this to be able to reach any window in any other terminal window on any host with max 4 keypresses)

This is an awfully specific request. However, I plan to soon add support for workspaces, which should give the user access to, for example, 40 panes within 2 keypresses, given a hypothetical 10 workspaces and 4 panes per workspace.

> Why choose Go? Just curious.

Good question! I chose Go for its go routines and channels. I somewhat wish I used Rust simply because of its elegance. 3mux's performance bottleneck right now is completely IO, so I don't think moving to Rust would make a noticeable difference to the end user apart from the installation process.

[stragies]

Thank you for replying!

I described my workflow, because since I discovered automatically grouped sessions on TMUX, I'd never want to use a terminal multiplexer without that, or comparable functionality.

What I do:

* Open new terminal with a hot-key

* This terminal automatically joins my local (default) session group

* All windows in this session group are now available

* Most windows connect to remote TMUXs

* With CTRL+ 4 keypresses I can navigate to any preexisting window/session, or create a new one locally (or on a remote host)

* After using the window, either i close the terminal, and/or the window, depending on if i want to keep this one.

* On the remote end, people can join my sessions, and can independently of me navigate in the remote window space.

* if I need to concurrently see two (probably different) windows of my local/remote window grid, I just open/auto-attach another terminal.

* the above makes it easy to "place another live tmux view" on a screen different than my main screen, for presentation, or teaching purposes.

Everybody (who previously used tmux in non-grouped mode) I've shown/explained this setup to, has setup their environment just like it afterwards.

Thanks for the other info too :)