So I wrote a book on tmux and use it every day, but I use i3 on my Linux box.
The main difference? tmux is a terminal multiplexer. So it's not going to handle the web browser stuff at all. Other than that, it's like Screen.
A lot of devs spend a lot of time in the Terminal, running scripts, background servers, etc. With tmux (like Screen) you can have them running and detach, and come back later.
Even with i3 I still find lots of room for tmux in my workflow when I'm in that environment.
tmux is also a hell of a tool for pair programming, and for managing remote servers.
But yea, if you're happy with i3, and you're using that to do Terminal splits, that's probably pretty great as is. tmux will remember the current working dir when you open new splits, and you can script it to launch your project workspace, but that's kind of just icing.
The main difference? tmux is a terminal multiplexer. So it's not going to handle the web browser stuff at all. Other than that, it's like Screen.
A lot of devs spend a lot of time in the Terminal, running scripts, background servers, etc. With tmux (like Screen) you can have them running and detach, and come back later.
Even with i3 I still find lots of room for tmux in my workflow when I'm in that environment.
tmux is also a hell of a tool for pair programming, and for managing remote servers.
But yea, if you're happy with i3, and you're using that to do Terminal splits, that's probably pretty great as is. tmux will remember the current working dir when you open new splits, and you can script it to launch your project workspace, but that's kind of just icing.