News for hackers. Stuff that matters.
Re:Show HN: Boo – Screen-style terminal multiplexer built on... by dgnemo on Thursday June 11, 2026 @06:23PM (#48497229)
can you share more on the tmux model vs boo?
[dead]
Re:Show HN: Boo – Screen-style terminal multiplexer built on... by dang on Thursday June 11, 2026 @08:45PM (#48498444)
Can you please not post AI-generated or AI-edited comments to HN? It's not allowed here - see https://news.ycombinator.com/newsguidelines.html#generated and https://news.ycombinator.com/item?id=47340079.

Of course, it's impossible to know for sure what was LLM processed or not, but some of your posts (like this one) are getting classified that way.

Re:Show HN: Boo – Screen-style terminal multiplexer built on... by kylecarbs on Thursday June 11, 2026 @09:11PM (#48498597)
Apologies, half of this indeed was. As I was iterating on the README this seemed apt, but I will refrain!
Re:Show HN: Boo – Screen-style terminal multiplexer built on... by dang on Thursday June 11, 2026 @10:20PM (#48499089)
Appreciated! The community feels strongly about this.
Re:Show HN: Boo – Screen-style terminal multiplexer built on... by drzaiusx11 on Thursday June 11, 2026 @08:22PM (#48498268)
Tmux is n clients to 1 server.

Screen is 1 server to 1 client.

In screen each client session is a fork of the screen server. In tmux there's one server and many client forks iirc.

Re:Show HN: Boo – Screen-style terminal multiplexer built on... by gguingff on Thursday June 11, 2026 @08:28PM (#48498313)
this is incorrect. you can have multiple clients using screen -x instead of screen -a
Re:Show HN: Boo – Screen-style terminal multiplexer built on... by drzaiusx11 on Thursday June 11, 2026 @08:55PM (#48498507)
I didn't say you couldn't have multiple clients, I said clients and servers are the same process forked. Or did someone add distinct client/server support to screen finally? I know theres a lot of stuff bolted onto screen over the years but I wasn't aware they dropped forked servers for the tmux model...
Re:Show HN: Boo – Screen-style terminal multiplexer built on... by drzaiusx11 on Thursday June 11, 2026 @10:08PM (#48499011)
Did a bit of digging; the first client gets forked to create the "server". The forked server then detaches and runs in the background. You're right that -x creates an entirely new, separate client process, unrelated to the OG client or the forked server.

Without -x though it works as originally described.

Edit: gnu screen 1.0 was originally released in 1987. The -x flag was released in screen 3.0 in the 90s. TIL