SkyArrow
Joined 4 years ago
Joined 4 years ago
1. Surfacing agents which are ready for further input
2. Letting you jump quickly to said agents
3. SSH session persistence, as I work on a beefy devbox at work. tmux also offers this.
I often need to juggle several streams of work at $job in parallel - such are the expectations.
Like you though, I'd much prefer to use my terminal directly with the indirection of an additional multiplexer like herdr or tmux - lower latency, easier scrollback & copying.
Session persistence can be solved by zmx [1].
Points 1 and 2 however are concerned with tracking the state of and navigating to parallel agents. I'm thinking about creating a TUI or SwiftUI app to handle those points in the way I like, but the challenge of integrating such an app with zmx and kitty to jump to the right panes both locally and over a devbox is a little daunting. Plus, I've found my devbox doesn't play too well with `ControlMaster auto` SSH config suggested by the zmx docs.
Works great even though it's labeled as an alpha.
Samsung shifts executives to six-day workweeks to 'inject a sense of crisis' https://news.ycombinator.com/item?id=40083470
Does it even matter if a centralised exchange increases its own latency when all market participants have to go through it? I can only think of the case when a security is listed on multiple exchanges, where the latency could mean a small arbitrage opportunity.
https://www.reddit.com/r/MechanicalKeyboards/comments/irmbqr...