Re:Show HN: Alacritty, a GPU-accelerated terminal emulator w...
by atombender on Friday January 06, 2017 @08:49PM
(#13341935)
Each to his own. Your setup sounds like a parody of the most outlandishly neckbeardy things devs can do in a shell. Most users don't want to deal with that sort of "layering".
Re:Show HN: Alacritty, a GPU-accelerated terminal emulator w...
by chriswarbo on Friday January 06, 2017 @09:25PM
(#13342042)
> Your setup sounds like a parody of the most outlandishly neckbeardy things devs can do in a shell.
I shaved off my neckbeard, I'll have you know! ;)
My setup's no more outlandish than using tmux or screen, except instead of typing `tmux` or `screen` I type `shell`, which aliases a `dtach dvtm` one-liner (with a few options sprinkled around, so I don't have to bother with config files).
The point is that none of these applications care if/how they're composed; if I want to add in or swap out something, it's just a change that one-liner.
Not so if, say, my terminal application were hard-coded to rely on tmux, as some sibling comments have suggested.
Re:Show HN: Alacritty, a GPU-accelerated terminal emulator w...
by netheril96 on Friday January 06, 2017 @08:59PM
(#13341961)
The famous saying: every problem can be solved by another layer of indirection, except the problem of too many indirections.
Everything's highly composable, e.g. I can switch out bash for zsh, fish, etc. I can switch out dtach for abduco. I can switch out dvtm for tmux or screen. I can switch out st for xterm or urxvt. And so on.
Adding an extra layer for scrollback, separate from a multiplexer, wouldn't disrupt anything, and would provide more flexibility for composition.