love the web assembly demo. By the way, I hope this kind of interface for the web becomes more mainstream in the future, I start to hate html / css cuz everything looks the same because of it (even in the train stations they use it for scheduling)
please do and let me know ! quick story fast, I'm working a loooot remotely. I'm using https://github.com/sanchxt/yoop to synchronize my keyboard. Since I'm using moonlight it's blazing fast. But when I work in the train I'm back to ssh. My quick tip would be to: build your own tools, build them once, use them forever. and rmux is exactly made for that, it's prefect for TUIs over ssh and low connection that needs to stay alive even if you get disconnected
correct... it's sad but recognition is a lot. After putting months of efforts, it's a risk I didn't want to take. And following tmux was like a red thread of life to code. Maybe in the future !
nice, zmx is a very nice approach. I did not want to take risks and change the expected behavior of the renown tmux. My main goal was 1) to rewrite tmux the modern way more elegantly (async, rust) and give it windows support 2) to give it a SDK. I think 1 window = 1 session is the right way, but it's a risky market move I didn't want to tackle for adoption. Maybe on a breaking v2 !
Hehe. I am building a multi agent orchestration system of course ;) I believe this is the future, agents speaking to one each other. It's very dirty with tmux
gobdovan nailed it. The CLI is a drop-in for existing tmux workflows; the SDK eases your flow when you'd otherwise be writing brittle send-keys + sleep + capture loop. But that's just one one of the use cases. rmux should be used to make beautiful TUI, something very dirty to do with tmux. Especially the day you want to do integration testing (playwright style)