[dead]
Superlogical
461–470 of 504 posts
Re: Superlogical
#462Earlier quoted context omitted.
Not really; not without understanding what am I missing. Why does Linux need a "multiplexer for all work," while Windows either already has one, doesn't need one, or couldn't use one?
A Multiplexer let's you run multiple terminals in one window, this is a new one. WindowsOS does not get as nice of tools as Linux generally.
Except you don't need a multiplexer for that. Essentially all modern terminals have tabs. Many have split-screen. Even windows ships with a half-decent terminal with tabs and multiple panes by default now!
A multiplexer's job is to do the whole multiple tabs/panes/windows thing independently of the terminal itself, but (a) the UX for eg. tmux is so much worse than that of a good terminal UI, and (b) you only need that if you plan on connecting remotely (see my other comment https://news.ycombinator.com/item?id=49108483).
Re: Superlogical
#463Earlier quoted context omitted.
I stopped running Claude on the terminal and use only the desktop app now. It had lots of advantages in my opinion. The terminal is really limited unfortunately, don’t know why so many devs still stick to it, and I used it for 30 years.
Interesting, which OS are you using? If linux, can you name 1-2 advantages the desktop has over the terminal?
I'm using Hermes but these should apply to any agent that has both TUI and GUI versions. The GUI version will have:
- drag and drop
- show document type, icon and filename
- inline images
- variable fonts, esp. monospace for code blocks
So GUI is mainly about readability. CLI works fine too but is inherently limited. I think GUI agents will keep pushing further in information layout, rendering, retrieval and interactivity. We're just at the beginning of it.
Re: Superlogical
#464Meta, won't comment on the site, won't click. I'm fed up with this category of click baity titles that are designed to be enigmatic rather than informative. The guideline do not mention this, apart maybe from: If the title includes the name of the site, please take it out, because the site name will be displayed after the link. I'd prefer HN if we made it a habit to editorialize such titles consisting solely of a Dom…
The actual header on the page is > We are building the multiplexer for all work. imo this would have been a better way to do the HN submission title (with or without [terminal]) > Superlogical: We are building the [terminal] multiplexer for all work
website is very vague - not useful content - no information, some gradient box without any content, team thats it. Super annoying landing page. Even if HN title is not descriptive the website is not helping to figure out what this is all about.
Re: Superlogical
#465I really like the bit where he transferred ownership of Ghostty to a non-profit, and is now building this new company on that as an open source dependency: > We will build on libghostty exactly as it was designed to be used: as a public building block for terminal applications. Superlogical will consume the same MIT-licensed components available to everyone else, and we will continue to upstream shared terminal work…
[deleted]
Re: Superlogical
#466[deleted]
Re: Superlogical
#467[dead]
Re: Superlogical
#468I feel like the main benefit of such a thing would be centralization. Part of the issue with the terminal ecosystem is precisely that everything's so fragmented and everybody needs to support arcane terminal protocols and wrap a billion wrappers around each other. The easiest way to solve this is to be a definer yourself rather than an integrator, which I think is what this is trying to be. If we could actually have…
There is PR somewhere in the mosh repo to support block cursor. Just build it manually. Mosh is abandoned, unfortunately.
Yeah I have my own forks for it, it's just annoying since usually I want to just install things on a machine and just "have it work". Mosh is also extra annoying because it depends on ssh and libcrypto stuff, which I have not found working with my current "install all my deps on a machine and run" workflow yet (e.g. from what I understand you basically have to compile from source for certain things that touch ssh and security; I wasn't able to get a portable git install either, instead I just trust the systemwide one and don't use old distributions).
I've found that I'm making compromises that keep integration with existing systems minimal at the cost of perfect aesthetics :(
Re: Superlogical
#469This sounds like a mashup of of several things I've been playing with lately... - pi-web ( https://pi-web.dev/ ): a web frontend for the Pi coding harness which can multiplex pi sessions across multiple machines - herdr ( https://herdr.dev/ ): a fairly polished agentic multiplexer TUI, can easily spawn or destroy windows based on subagent activity - firstmate ( https://github.com/kunchenguid/firstmate ): a meta envir…
These tools all assume you have machines to run the agents on. But for parallel agents I'm pretty convinced you want each agent on its own isolated devbox running your dev environment (not e.g. worktrees on one box) - which isn't trivial to set up and manage. I'm working this with https://boxes.dev - a workspace for launching and managing claude + codex sessions, each running in its own cloud devbox. We launched with…
>for parallel agents I'm pretty convinced you want each agent on its own isolated devbox running your dev environment (not e.g. worktrees on one box)
Why?
Re: Superlogical
#470Earlier quoted context omitted.
Not really; not without understanding what am I missing. Why does Linux need a "multiplexer for all work," while Windows either already has one, doesn't need one, or couldn't use one?
A Multiplexer let's you run multiple terminals in one window, this is a new one. WindowsOS does not get as nice of tools as Linux generally.
After using a tiling WM, it feels like this is a window manager job. It even works for non-terminal applications.